Route attendee follow-up work automatically
The right owner gets the next action before it becomes a dropped ball.
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
After an event, founders often remember the conversation but forget who owns the follow-up.
- Make ownership explicit immediately
- Reduce post-event mental bookkeeping
- Keep follow-ups connected to the engineering workspace
Setup
Build it in a few focused steps.
- 1Connect Eventbrite and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3In one instruction, tell Notis how to assign the matching GitHub issue when attendee activity indicates a follow-up.
- 4Select the webhook trigger, choose the reporting channel, and test with one real attendee record.
Questions about this workflow
Can Notis decide who owns the follow-up?
Yes. State the ownership rule in the prompt, such as assigning technical questions to the engineering lead.
What starts the automation?
An Eventbrite event or custom backend must send an HTTP request to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Eventbrite to GitHub. A trigger fires from one place; an action lands in another.
Eventbrite triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
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.
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.
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 Eventbrite 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.