Route Amcards bug reports to a GitHub issue owner
Make reported bugs easier to pick up. Send the card report to Notis and assign its matching GitHub issue to the named investigator.
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 bug report can sit in outreach notes while the related GitHub issue waits without an owner.
- Connects bug reports to the issue that needs investigation.
- Makes ownership clear when the report includes an intended assignee.
- Avoids assigning an issue when the report does not identify one.
Setup
Build it in a few focused steps.
- 1Connect Amcards and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to match incoming Amcards bug reports to an existing GitHub issue and add the named assignee only when the issue and assignee are clear.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real bug report that identifies an issue and an assignable GitHub username.
Questions about this workflow
Does this workflow create or investigate bugs?
No. It adds an assignee to an existing issue. The report needs to identify the issue and an assignee.
What happens if the user cannot be assigned?
GitHub may ignore the change when the user is not assignable or the authenticated account lacks the required access. Review run reports for unsuccessful assignments.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Amcards to GitHub. A trigger fires from one place; an action lands in another.
Amcards 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.
Amcards 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.