Keep recognition follow-ups attached to their GitHub issue
When a CardClan recognition card calls out a follow-up, have Notis assign the existing GitHub issue to the person named in the handoff.
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 follow-up mentioned around a team celebration can disappear when it is separate from the issue tracker.
- Put a named owner on an existing issue.
- Reduce manual context switching after recognition moments.
- Keep the requested follow-up tied to the correct repository issue.
Setup
Build it in a few focused steps.
- 1Connect CardClan and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to add the named GitHub assignee to the specified existing issue when a CardClan recognition follow-up is handed off.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real follow-up and confirm the issue number and assignee are correct.
Questions about this workflow
Will this create a new GitHub issue?
No. The selected action adds or removes assignees on an existing issue. Include the repository and issue number in the handoff.
What if the account cannot assign the person?
GitHub may silently ignore the change if the authenticated user lacks push access to the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CardClan to GitHub. A trigger fires from one place; an action lands in another.
CardClan 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.
CardClan 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.