Keep deal risks visible on the GitHub issues they affect
Send an Affinity deal update to Notis and label the GitHub issue it calls out, so engineering follow-up stays connected to the deal context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Deal risks in Affinity can be easy to miss when the related engineering work lives in GitHub.
- Carry deal context into the named GitHub issue.
- Make risk-related work easier to spot during issue triage.
- Avoid searching manually across Affinity and GitHub.
Setup
Build it in a few focused steps.
- 1Connect Affinity and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to read the submitted Affinity update and label only the GitHub issue it explicitly identifies.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with one real deal update that includes a repository, issue number, and risk context.
Questions about this workflow
Does this automation choose a GitHub issue based on a company name alone?
No. The instruction should require an explicit repository and issue reference in the Affinity update so Notis can target the intended issue.
Will it create missing labels?
The selected GitHub action adds labels and creates labels that do not already exist. State the intended label clearly in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinity to GitHub. A trigger fires from one place; an action lands in another.
Affinity 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.
Affinity 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.