Make Customer Feature Requests Easier to Find in GitHub
Pass the issue and customer-request context to Notis and apply the labels your team uses to triage it.
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 requests can be recorded in CRM while the related GitHub issue remains difficult for the team to find.
- Make customer-driven issues easier to group in GitHub.
- Apply labels supplied with the request context.
- Reduce manual triage steps during product conversations.
Setup
Build it in a few focused steps.
- 1Connect Capsule CRM and GitHub once in the Notis portal.
- 2Create an automation in Automations > New Automation and name it for feature request labeling.
- 3In one instruction, tell Notis to use the issue reference and requested labels in the incoming feature request to label the GitHub issue.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real feature request linked to a GitHub issue.
Questions about this workflow
Do requested labels need to exist first?
No. The listed GitHub action creates labels that do not already exist.
Can Notis infer the right issue from a customer name?
Include the GitHub issue reference or give Notis a clear matching rule and enough returned data to identify the issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Capsule crm to GitHub. A trigger fires from one place; an action lands in another.
Capsule crm 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.
Capsule crm 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.