Make customer signals visible on GitHub issues
Turn a high-intent visit or conversion signal into a label on the GitHub issue already tracking the related product work.
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
Customer intent is visible in lead intelligence, but the team misses it when prioritizing the connected product issue.
- Surface customer context alongside the work item the team already uses.
- Make lead-driven work easier to scan and discuss.
- Let Notis interpret the webhook context and apply the requested label.
Setup
Build it in a few focused steps.
- 1Connect Bread & Butter and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis which lead milestones matter and to add the corresponding label to the existing issue identified in the request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real lead signal that includes an issue reference and the intended label.
Questions about this workflow
Will the action create the label if it does not exist?
Yes. GitHub's add-labels action creates labels that do not already exist in the repository.
Can the signal be used without an issue reference?
The action needs a repository issue to label. Include the repository and issue number in the webhook or provide a reliable way to identify the existing issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bread & Butter to GitHub. A trigger fires from one place; an action lands in another.
Bread & Butter 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.
Bread & Butter 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.