Give profile sync regressions an owner
Make synchronization problems easier to investigate by attaching an owner at intake.
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
Profile sync regressions can be noticed in customer data before anyone takes ownership in GitHub.
- Make a profile synchronization regression actionable in GitHub.
- Use the signal context to route investigation to a suitable assignee.
- Reduce time spent finding an owner after the issue is reported.
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, define a profile sync regression and how to select its related issue and assignee.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Send one real regression signal to test the flow.
Questions about this workflow
Can this create a new GitHub issue?
No. The available action assigns users to an existing issue, so provide the related issue in the incoming request or instruction.
What if no suitable owner is clear?
Set the instruction to assign only when an eligible owner can be identified, and review the run report when the context is incomplete.
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.