Route VIP follow-up to a GitHub issue owner
When an Attio update flags a customer as a priority, have Notis assign the related GitHub issue so the follow-up has a clear owner.
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
Priority customer follow-up can get lost when relationship context lives in Attio and engineering work lives in GitHub.
- Connect customer context to a named issue owner.
- Reduce manual handoffs between relationship and engineering work.
- Keep issue assignment tied to an explicit Attio signal.
Setup
Build it in a few focused steps.
- 1Connect Attio and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In plain language, tell Notis to find the related GitHub issue and assign the appropriate owner when an Attio priority signal arrives.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test the automation with one real Attio signal and related GitHub issue.
Questions about this workflow
Does Attio provide a native trigger event here?
No. Start this workflow with a Notis webhook request when the relevant Attio signal is ready.
How does Notis know which issue to assign?
Describe the relationship between the Attio record and GitHub issue in your instruction. If the records cannot be matched from available data, supply the matching detail.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Attio to GitHub. A trigger fires from one place; an action lands in another.
Attio triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Attio and GitHub, 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 GitHub.