Assign follow-up issues from Cardly responses
When a Cardly response calls for code follow-up, pass it to Notis and get the related issue in front of an assignee.
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 response that needs engineering attention can be read and still fail to reach an owner.
- Put actionable feedback in front of an issue owner.
- Reduce manual handoffs between outreach and engineering.
- Use clear instructions for how to choose an assignee.
Setup
Build it in a few focused steps.
- 1Connect Cardly and GitHub once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Describe how to find the related issue, decide whether it needs follow-up, and choose an eligible assignee in one instruction.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Send one real response example and review the issue assignment.
Questions about this workflow
Can this workflow decide who should own the issue?
Yes, if your instruction provides a usable rule or the webhook includes enough context. Otherwise, tell Notis to report the missing information without assigning anyone.
What happens when no GitHub issue matches?
Have the automation report that it could not identify an issue so you can supply the right context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cardly to GitHub. A trigger fires from one place; an action lands in another.
Cardly 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.
Cardly 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.