Check customer proof when public messaging changes
A small README edit can change the story prospects see first.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Get Testimonial
Tool to retrieve details of a specific testimonial by its unique identifier. use after obtaining the testimonial id to fetch its full details.
Why this helps
Public claims drift away from customer evidence as product documentation evolves.
- Catches unsupported or outdated claims
- Makes documentation review more evidence-based
- Reduces anxiety before publishing important edits
Setup
Build it in a few focused steps.
- 1Connect GitHub and Endorsal to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to retrieve Endorsal proof relevant to changed README claims.
- 3Select the GitHub repository README changed trigger and choose a channel for run reports.
- 4Test it with one README edit and review the returned evidence.
Questions about this workflow
Can this focus on a specific README section?
Yes. Include the section or claim type in the plain-language instruction.
Does Notis publish the README automatically?
No. It provides evidence for review before you decide to publish.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Endorsal. A trigger fires from one place; an action lands in another.
GitHub triggers
Endorsal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Testimonial
Tool to submit a new testimonial. use when adding customer feedback to your endorsal account after gathering input.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get AutoRequest Campaign
Tool to retrieve a specific autorequest campaign by its unique identifier. use when you need to fetch details of an existing autorequest campaign.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Get Contact
Tool to retrieve details of a specific contact by its unique identifier. use when you have the contact id and need to fetch complete contact details.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Get Tag
Tool to retrieve details of a specific tag by its unique identifier. use when you have a tag id and need full tag metadata.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Testimonial
Tool to retrieve details of a specific testimonial by its unique identifier. use after obtaining the testimonial id to fetch its full details.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Widget
Tool to retrieve details of a specific widget by its unique identifier. use when you need full widget details before editing or analysis.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
List AutoRequest Campaigns
Tool to retrieve a list of all autorequest campaigns. use when you need to view both active and inactive campaigns.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
List Contacts
Tool to retrieve all contacts associated with your account. use when you need to browse or manage your contact list after authentication.
Connect any two apps with Notis in the middle.
GitHub and Endorsal, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Endorsal.