Keep pending deployment transactions visible in GitHub
When a deployment transaction is still pending, make its tracking issue easy to spot without switching tools.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A transaction can sit pending while its GitHub issue looks unchanged, leaving the team to remember to update it manually.
- Make pending deployment work visible in the issue list.
- Reduce manual status checks across Blocknative and GitHub.
- Keep the issue as the shared place for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Blocknative and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis to read the webhook transaction status and add the agreed pending label to the specified GitHub issue when it is pending.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real pending transaction and its tracking issue.
Questions about this workflow
What starts this workflow?
An HTTP request to the Notis webhook starts it. Include enough transaction and issue context for Notis to identify the relevant record.
Does Blocknative provide the webhook trigger event here?
No source event is listed. This workflow uses a Notis webhook trigger, with transaction details supplied in the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to GitHub. A trigger fires from one place; an action lands in another.
Blocknative 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.
Blocknative 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.