Make relationship follow-up visible in GitHub
Give recurring relationship reviews a concrete next step: label the GitHub issue connected to an Attio record that needs attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A founder can spot a relationship going quiet in Attio and still forget to surface the engineering task that needs attention.
- Turn a recurring Attio review into visible GitHub follow-up.
- Make related issues easier to spot during triage.
- Reduce the need to remember a second manual update.
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 name it for the relationship review.
- 3Tell Notis in one plain language instruction to identify stale Attio relationships and add an appropriate label to the matching GitHub issue.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real stale relationship and its related issue.
Questions about this workflow
Will Notis decide what counts as stale?
State the rule in your instruction and ensure Attio provides enough relationship history to evaluate it. Supply any missing baseline or definition.
What if the label does not exist in GitHub?
The selected GitHub action can create labels that do not already exist.
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.