Turn Amcards feature requests into labeled GitHub issues
Keep product feedback visible where your team plans and ships work. Send card feedback to Notis and label the matching GitHub issue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Feature ideas shared through outreach can get buried before they reach the team's issue queue.
- Keeps card feedback connected to the issue your team already tracks.
- Makes feature requests easier to find during triage.
- Leaves unmatched feedback untouched when the issue is unclear.
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 use incoming Amcards card feedback to identify a matching GitHub issue and add the feature-request label only when the match is clear.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real card response that identifies a GitHub issue.
Questions about this workflow
What should the webhook request include?
Include the card feedback and enough context, such as a repository and issue number or a clear issue reference, for Notis to identify the intended GitHub issue.
Will this create a GitHub issue if none matches?
No. This workflow adds a label to an existing issue. Ask Notis to report feedback without a clear match so you can review it.
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.