Keep GitHub issues organized from Botbaba conversations
Send a conversation to Notis and have its key issue context reflected in GitHub labels, so triage stays close to where work happens.
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
Useful issue context gets lost when a conversation ends and someone has to manually classify the follow-up in GitHub.
- Reduce manual issue triage after a Botbaba conversation
- Keep existing GitHub labels useful and consistent
- Turn conversation context into a clear next step
Setup
Build it in a few focused steps.
- 1Connect Botbaba and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to use the submitted conversation context to choose appropriate labels for the specified GitHub issue and apply them.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real conversation and GitHub issue.
Questions about this workflow
What starts this automation?
A webhook starts it when an HTTP request is sent to the Notis automation.
Does it create labels?
The GitHub action adds the requested labels and creates labels that do not already exist.
Does Notis know which issue to label?
The request or instruction needs to identify the GitHub repository and issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botbaba to GitHub. A trigger fires from one place; an action lands in another.
Botbaba 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.
Botbaba 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.