Make recurring BotMape themes visible in GitHub
On a regular review schedule, use conversation summaries to find related issues and add concise theme labels.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Recurring agent or customer themes are hard to spot when conversation summaries and GitHub issues are reviewed at different times.
- Make recurring themes easier to see during issue review.
- Label matching issues in one scheduled pass.
- Create labels that are missing as part of the GitHub action.
Setup
Build it in a few focused steps.
- 1Connect BotMape and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, tell Notis to review the BotMape conversation summaries available for the run, identify supported themes, and add those labels to matching GitHub issues.
- 4Pick the recurring schedule trigger and choose where run reports go.
- 5Test with one real review set and check the issue matches and labels.
Questions about this workflow
Does a schedule automatically provide conversation summaries?
Notis cron starts the automation on a recurring schedule. Ensure the prompt or connected data source makes the summaries available; BotMape has no listed trigger event here.
Will it create labels?
Yes. The GitHub action creates labels that do not already exist when adding labels to an issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotMape to GitHub. A trigger fires from one place; an action lands in another.
BotMape 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.
BotMape 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.