Add Clay account context to GitHub issue labels
Give customer-related GitHub issues labels that make their account context easy to see.
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
Customer context sits in Clay while GitHub issues stay hard to recognize and triage.
- Spot issues tied to important accounts faster
- Reduce manual context switching between Clay and GitHub
- Keep issue labels aligned with incoming account context
Setup
Build it in a few focused steps.
- 1Connect Clay and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis the outcome in plain language.
- 3In one instruction, ask Notis to use the account context in each Clay webhook request to label the matching GitHub issue.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real Clay record and matching GitHub issue.
Questions about this workflow
How does Clay start this workflow?
Configure Clay to send an HTTP request to the Notis webhook when the relevant account or issue context is ready.
Can the workflow create labels?
The GitHub action adds requested labels, creating labels that do not already exist in the repository.
What if the webhook does not identify a GitHub issue?
Include enough repository and issue context in the request for Notis to identify the intended issue; otherwise the run may not be able to proceed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clay to GitHub. A trigger fires from one place; an action lands in another.
Clay 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.
Clay 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.