Keep follow-up ownership clear from BotMape conversations
When a conversation highlights a follow-up, send its context to Notis and update the matching GitHub issue's assignees.
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
Follow-up owners are easy to lose when conversation notes and engineering issues live in separate places.
- Make ownership changes while the relevant conversation context is fresh.
- Add or remove issue assignees based on an explicit follow-up request.
- Reduce manual coordination between conversation review and issue triage.
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 give it a clear name.
- 3In one instruction, tell Notis to find the related issue and update assignees only when the incoming conversation specifies an owner change.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real conversation follow-up that identifies a GitHub issue and an assignee.
Questions about this workflow
Can this infer who should own an issue?
The prompt can ask Notis to use ownership explicitly stated in the incoming context. If the context does not identify an owner, it should leave assignees unchanged.
What if the account cannot update the issue?
GitHub may silently ignore assignee changes if the authenticated user lacks push access to the repository.
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.