Route account-related GitHub issues by Clay ownership
Send an issue to the person responsible for its account, using ownership context from Clay.
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
Issues tied to customer accounts can sit unassigned when ownership lives in another tool.
- Reduce time spent finding the right issue owner
- Keep account follow-up connected to engineering work
- Make ownership updates actionable when Clay sends them
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 assign the matching GitHub issue to the eligible GitHub user identified by Clay ownership context.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real record and issue, confirming the owner can be assigned.
Questions about this workflow
Does Clay provide a GitHub assignee automatically?
The webhook request needs to include an ownership value that Notis can use to identify an eligible GitHub user.
Can this action assign anyone?
GitHub can silently ignore assignment changes if the authenticated user lacks push access to the repository. The target user also needs to be assignable.
What if there is no matching owner?
Have the instruction direct Notis to leave the issue unchanged and report the missing or ambiguous ownership context.
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.