Bring account research into GitHub issue triage
When a Bigpicture update includes a linked GitHub issue, add the labels that fit the qualification result and company research.
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
Account context can be easy to lose when it lives in research records while follow-up happens in GitHub.
- See qualification context in the linked issue
- Reduce manual handoff from research to engineering
- Skip updates when the webhook has no valid issue reference
Setup
Build it in a few focused steps.
- 1Connect Bigpicture io and GitHub once in Notis.
- 2Create an automation in Notis from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to add relevant existing labels to the linked issue using the Bigpicture qualification and research; skip if the payload lacks a repository or issue number.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real Bigpicture update that includes a GitHub repository and issue number.
Questions about this workflow
Does this create a GitHub issue?
No. This workflow adds labels to an existing issue linked in the webhook payload.
What if the issue or labels are missing?
Tell Notis to skip the update and report that the issue reference or suitable label was missing. GitHub can create labels that do not already exist, so ask Notis to use existing labels when that is your intent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bigpicture io to GitHub. A trigger fires from one place; an action lands in another.
Bigpicture io 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.
Bigpicture io 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.