Connect GitHub to Delighted
When something happens in GitHub, Notis takes the next step in Delighted. 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 Delighted
Survey customers after a successful deployment
Send a Delighted survey after a GitHub deployment reaches success so founders can catch customer sentiment while the release is fresh.
Validate customer impact for every new pull request
Create a targeted Delighted survey workflow when a new GitHub pull request describes a customer-facing change.
Survey customers when a product request becomes an issue
Use newly created GitHub issues to schedule Delighted surveys for customers connected to the request or problem.
Add customers to feedback autopilot after approved work
Enroll relevant customers in Delighted Autopilot when a GitHub pull request receives an approved review.
Ask for feedback after substantial PR iteration
Schedule a Delighted survey when a GitHub pull request receives a new commit, helping founders validate revisions without manual chasing.
Collect feedback when a pull request closes
Use a closed or merged GitHub pull request as a handoff point for a Delighted customer survey.
Send an SMS check-in after a new deployment
Use a new GitHub deployment to add a relevant customer to Delighted SMS survey delivery for fast release feedback.
Enroll affected customers after a new issue arrives
Add customers to Delighted email Autopilot when a new GitHub issue signals an ongoing product concern.
Survey customers when an issue is resolved
Schedule a Delighted survey when a GitHub issue closes, helping founders confirm that the resolution worked in practice.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Delighted. A trigger fires from one place; an action lands in another.
GitHub triggers
Delighted actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Person to Autopilot Email
Adds a person to automated email surveys or updates their profile details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Person to Autopilot SMS
Adds a person to automated SMS surveys or updates their profile details.
New Workflow Artifact Created
Create or Update Person
Creates or updates a person and schedules a survey email.
Branch Changed
Delete Pending Survey Requests
Cancels all pending survey requests for a person.
New Branch Created
Delete Person
Permanently deletes a person and all associated data.
Check Run Status / Conclusion Changed
Get Autopilot Email Configuration
Retrieves the current email Autopilot configuration.
Check Suite Status / Conclusion Changed
Get Autopilot SMS Configuration
Retrieves the current SMS Autopilot configuration.
New Code Scanning Alert Created
List Autopilot SMS Memberships
Lists people enrolled in SMS Autopilot.
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 through 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 Delighted
Connect any two apps with Notis in the middle.
GitHub and Delighted, 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 Delighted.