Route Blooio escalations to a GitHub issue owner
Send the escalation to Notis, and let it handle the GitHub follow-up.
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
Important escalations arrive in chat, then get lost while you decide who should own the code follow-up.
- Creates a clear owner for follow-up
- Reduces switching between messaging and GitHub
- Keeps issue assignment decisions tied to escalation context
Setup
Build it in a few focused steps.
- 1Connect Blooio and GitHub once in the Notis portal.
- 2Create an automation by telling Notis the outcome you want, or use Automations, New Automation in the portal.
- 3In one instruction, ask Notis to interpret the incoming escalation and assign the relevant GitHub issue to an appropriate available assignee.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real Blooio escalation and review the assignment.
Questions about this workflow
Does Blooio provide a trigger event for this workflow?
No. Use a Notis webhook and send the relevant Blooio data to its HTTP endpoint.
Can Notis determine the issue and assignee automatically?
It can use the context and GitHub information available to it. If the intended issue or assignee is unclear, supply a decision rule in your instruction or ask Notis to report the ambiguity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blooio to GitHub. A trigger fires from one place; an action lands in another.
Blooio 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.
Blooio 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.