Assign GitHub follow-up from a Clearout lead alert
Put the next step on the right person when a useful lead alert arrives.
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
A lead can need a product or integration follow-up, but ownership is easy to lose between research and issue tracking.
- Make issue ownership explicit
- Reduce dropped follow-up after a lead alert
- Keep the handoff in GitHub
Setup
Build it in a few focused steps.
- 1Connect Clearout and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to match each incoming lead alert to an existing issue and assign it to the named or agreed owner; ask it to report when no owner is supplied.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real alert that identifies an issue and an assignable GitHub user.
Questions about this workflow
Will the workflow invent an owner if the report does not name one?
No. The report should provide an owner or your instruction should define a grounded assignment rule. Otherwise, have Notis report that ownership is missing.
What if the user cannot be assigned?
GitHub may ignore assignment changes when permissions are insufficient. Ask Notis to report the result so you can review it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clearout to GitHub. A trigger fires from one place; an action lands in another.
Clearout 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.
Clearout 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.