Assign launch follow-up issues automatically
When a launch lands, the next owner should be obvious. Notis can make that handoff while the context is fresh.
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
Post-launch fixes and follow-ups sit unassigned because nobody remembers to route them.
- Makes ownership explicit
- Prevents launch tasks from sitting idle
- Saves a separate triage session
Setup
Build it in a few focused steps.
- 1Connect BulkPublish and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it conversationally.
- 3Describe the outcome as one instruction: assign matching GitHub launch issues to the responsible owner when BulkPublish reports the launch.
- 4Pick the webhook trigger and choose where Notis should report runs.
- 5Test with one real launch event.
Questions about this workflow
How does Notis identify the owner?
Your plain-language instruction can define the owner using the campaign context and the people or rules you name.
Will this create new GitHub issues?
No. This workflow assigns existing issues.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BulkPublish to GitHub. A trigger fires from one place; an action lands in another.
BulkPublish 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 BulkPublish and GitHub. Any 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.