Give advice driven feature investigations an owner
Turn a product advice signal into a clear next step for the person investigating it.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Potential product opportunities can remain in the issue queue without someone accountable for assessing them.
- Give investigation work a clear owner.
- Route based on the advice and issue context already in the request.
- Make it easier to follow up on potential product opportunities.
Setup
Build it in a few focused steps.
- 1Connect Bluebarry and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, state which advice merits a feature investigation and how to identify the issue and eligible assignee.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Send one real feature advice signal to test the flow.
Questions about this workflow
Will this decide whether to build the feature?
No. It assigns an existing issue for investigation. The product decision remains with your team.
What if the signal does not include an issue?
The action needs an existing issue to assign. Include its reference in the request or follow up after issue creation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bluebarry to GitHub. A trigger fires from one place; an action lands in another.
Bluebarry 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.
Bluebarry 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.