Put a clear owner on every launch follow-up
Turn a Beamer launch follow-up into a GitHub issue with the right people attached, so the next step has an owner.
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
After a launch announcement, follow-up can sit in a thread without a clear person responsible for the GitHub work.
- Makes ownership visible on launch-related issues.
- Keeps Beamer context close to the engineering follow-up.
- Cuts manual handoff after a release or feature announcement.
Setup
Build it in a few focused steps.
- 1Connect Beamer and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to use the incoming Beamer launch context to find the matching GitHub issue and add the named GitHub assignees.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real launch follow-up and issue reference.
Questions about this workflow
What starts this workflow?
A Notis webhook starts it when an HTTP request arrives. Beamer does not provide a trigger event here, so the request needs to include the launch context Notis should use.
Can the workflow determine an owner from the announcement alone?
Only if the Beamer context includes the owner or your instruction provides a clear rule. Otherwise, supply the GitHub usernames in the request or instruction.
What if the issue cannot be found?
Notis can report that it could not identify a matching issue. Include an issue reference in the webhook context when available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beamer to GitHub. A trigger fires from one place; an action lands in another.
Beamer 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.
Beamer 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.