Connect GitHub to Endorsal
When something happens in GitHub, Notis takes the next step in Endorsal. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from GitHub to Endorsal
Turn positive closed issues into testimonials
When a GitHub issue closes with a clear customer win, create a draft-ready Endorsal testimonial from the outcome and supporting context.
Capture approved pull request feedback
When a pull request review is approved and includes customer-impact context, create an Endorsal testimonial from the validated result.
Review testimonials when a repository gains a star
When a new GitHub stargazer arrives, list Endorsal testimonials for a selected tag so you can quickly identify proof relevant to the product's growing audience.
Check proof after a release update
When a GitHub release changes, retrieve a selected Endorsal testimonial to help validate whether the release story has supporting customer evidence.
Document successful production deployments
When a GitHub deployment succeeds, create an Endorsal testimonial from the deployment context when it clearly represents a customer-visible improvement.
Capture customer impact from new issues
When a GitHub issue arrives with a detailed customer result or quote, create an Endorsal testimonial so valuable language is not lost during triage.
Turn proof-rich feature requests into candidates
When a new GitHub issue documents a strong customer need or desired outcome, create an Endorsal testimonial candidate for later review.
Capture proof when customer-focused PRs merge
When a pull request closes or synchronizes, create an Endorsal testimonial when the change delivers a documented customer-facing result.
Review proof after customer PR updates
When a customer-focused pull request receives a new commit, retrieve the most relevant Endorsal testimonial to keep implementation decisions connected to user evidence.
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
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.
Create Testimonial
Tool to submit a new testimonial. use when adding customer feedback to your endorsal account after gathering input.
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 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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 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.
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.
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.
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.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
List AutoRequest Campaigns
Tool to retrieve a list of all autorequest campaigns. use when you need to view both active and inactive campaigns.
Commit Event
Triggered when a new commit is pushed to a repository.
List Contacts
Tool to retrieve all contacts associated with your account. use when you need to browse or manage your contact list after authentication.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it trough Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect GitHub and Endorsal
Connect any two apps with Notis in the middle.
Not just GitHub and Endorsal. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Endorsal.