Send each creative review issue to its owner
When an asset is ready, the right reviewer can get the GitHub issue without someone remembering to assign it by hand.
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
Review tasks get delayed when ownership is not recorded alongside a completed asset.
- Makes review ownership explicit
- Cuts down on manual issue housekeeping
- Uses the reviewer information supplied with the request
Setup
Build it in a few focused steps.
- 1Connect Bannerbear 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 assign the related GitHub issue to the reviewer included in the incoming render request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real render, issue reference, and assignable reviewer.
Questions about this workflow
Can Notis choose a reviewer if none is supplied?
The reviewer must be identified in the request or otherwise supplied in your instruction. This action adds or removes assignees and may be silently ignored without push access.
Does the action create a GitHub issue?
No. It adds an assignee to an existing issue identified in the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bannerbear to GitHub. A trigger fires from one place; an action lands in another.
Bannerbear 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.
Bannerbear 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.