Finish a pending fork run after the hardware check passes
When a hardware check is the last required signal, use its webhook to approve the identified fork run awaiting review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Approve a workflow run for a fork pull request
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Why this helps
A manual approval can be missed after a hardware check has already completed, leaving a valid run waiting.
- Connect a completed hardware check to the specific waiting run.
- Reduce follow-up for runs that require manual approval.
- Keep approval grounded in an explicit check result and run reference.
Setup
Build it in a few focused steps.
- 1Connect Bolt IoT and GitHub once in Notis.
- 2Create an automation from any channel or in Automations, New Automation.
- 3Tell Notis to approve the referenced fork pull request workflow run only when the webhook reports the required hardware check passed.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with a real passing check and a fork workflow run awaiting approval.
Questions about this workflow
Will this approve any run from a fork?
It should act only on the specific run identified by the webhook and only under the condition in your instruction.
What if the run does not need manual approval?
This action is intended for a fork pull request workflow run that is awaiting manual approval.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolt iot to GitHub. A trigger fires from one place; an action lands in another.
Bolt iot 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.
Bolt iot 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.