Sync Customer Events to Team Permissions via Webhook
When your third-party tools send events via webhook (e.g., a customer upgrade from an external system), Notis automatically updates which GitHub repositories your teams can access. Sync external tools to your GitHub without manual configuration.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Your CRM or support tool tracks customer changes, but GitHub team permissions stay static; team members don't have access to resources their customers need.
- External tool events automatically trigger GitHub access updates
- Teams get access to exactly the resources their customers need
- No manual permission juggling between third-party tools and GitHub
- Reduces cognitive overhead of tracking distributed customer and access data
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Create a webhook automation: 'When you receive a webhook from [external tool], update the [TeamName] repository permissions to [access level]'.
- 3Tell Notis how to interpret the webhook data: 'if the event says upgrade=true, give admin access; if upgrade=false, give read access'.
- 4Notis will generate a unique webhook URL—configure your external tool to send events to that URL.
Questions about this workflow
What format should my webhook payload be in?
Notis accepts standard JSON webhooks. Include fields like customer_id, event_type, and your custom data. Notis will parse and route intelligently.
Can I test the webhook before going live?
Yes. Notis gives you a unique webhook URL and a test panel. Send a test event and verify the GitHub permission change happens as expected.
What if different customers need different teams?
Tell Notis the mapping in your automation: 'if webhook customer_id is X, update team A; if customer_id is Y, update team B'. Notis routes accordingly.
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 985+ 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.