Give every Botpress escalation a GitHub owner
Notis reads the escalation context and adds the appropriate assignee to the related GitHub issue, turning a customer conversation into owned work.
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
Escalated conversations often produce a backlog item but no clear owner, forcing founders to chase someone later or carry the task mentally.
- Creates immediate accountability for high-signal conversations
- Cuts down on Slack pings and manual issue reassignment
- Keeps the responsible teammate visible where the work happens
Setup
Build it in a few focused steps.
- 1Connect your Botpress and GitHub accounts to Notis.
- 2Ask Notis to create an automation that assigns the related GitHub issue whenever Botpress sends an escalation webhook.
- 3Select the incoming webhook trigger and a channel for concise run confirmations.
- 4Test with a genuine escalation that references an issue and verify the intended teammate is assigned.
Questions about this workflow
How does Notis know whom to assign?
State your ownership rules in the plain-language prompt, such as assigning billing problems to one maintainer and API problems to another.
What if a person cannot be assigned?
GitHub may ignore an assignee who is not eligible for the repository. Use a run-report channel so Notis can surface unsuccessful or incomplete assignments.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to GitHub. A trigger fires from one place; an action lands in another.
Botpress triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Botpress and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.