Route Issues Automatically From External Systems
When your external tools send a webhook (e.g., a support ticket, customer request, or monitoring alert), Notis automatically creates and assigns a GitHub issue to the right person—no manual ticket triage, no forgotten action items.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Support tickets pile up in your support tool, but engineering doesn't see them; critical issues get buried, context-switching happens when someone finally notices, time-sensitive requests miss deadlines.
- External system events instantly become assigned GitHub issues
- Correct team member is assigned automatically based on your rules
- No manual ticket triage or forwarding needed
- Reduces cognitive load: critical issues don't get lost in tool gaps
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Create a webhook automation: 'When you receive a webhook, create a GitHub issue with title from the webhook's subject field, and assign it to [team member]'.
- 3Tell Notis your assignment logic: 'if webhook priority is urgent, assign to Alice; if standard, assign to Bob'.
- 4Notis generates a unique webhook URL—configure your external tool to POST events to that URL.
Questions about this workflow
What if I want different assignment rules based on issue type?
Tell Notis: 'if webhook type is bug, assign to QA-lead; if type is feature, assign to product-owner'. Notis routes based on any webhook field.
Can I add labels or milestone automatically?
Yes. Tell Notis: 'add label [webhook-category] and milestone [sprint-name] to each issue'. Notis applies metadata from the webhook.
What if the assigned person is out?
Tell Notis to have a fallback: 'if primary assignee is out, assign to backup person'. Notis respects out-of-office status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to GitHub. A trigger fires from one place; an action lands in another.
Stripe triggers
GitHub actions
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Product Created Trigger
Triggered when a product is created in Stripe
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Stripe and GitHub. 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 GitHub.