Turn Bright Data findings into labeled GitHub issues
Send a Bright Data research result to Notis and let it find matching GitHub issues, then label them for the next step.
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
Research and issue triage happen in separate places, so useful findings can sit without a clear next action.
- Bring public research into the issue queue
- Make related issues easier to scan
- Reduce manual switching between research and GitHub
Setup
Build it in a few focused steps.
- 1Connect Bright Data MCP and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to use incoming Bright Data findings to identify matching open issues and add a concise label that reflects the finding.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real research result and review the issues Notis labeled.
Questions about this workflow
Does Bright Data start this automation on its own?
Bright Data MCP has no trigger events in this setup. A Notis webhook starts the automation when it receives an HTTP request containing the research result.
Can Notis invent labels for GitHub?
The selected GitHub action adds labels, and its event description says labels that do not exist are created. Tell Notis which labels to use or how to name them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bright Data MCP to GitHub. A trigger fires from one place; an action lands in another.
Bright Data MCP 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.
Bright Data MCP 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.