Approve a trusted GitHub fork workflow from a release webhook
Avoid losing a release handoff to one manual approval step.
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 single pending approval can stall work after everyone has moved on.
- Keeps an approved release path moving
- Reduces manual handoffs
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis once.
- 2Create a new automation and describe the trusted workflow approval rule.
- 3Choose an incoming Notis webhook as the trigger.
- 4Select the channel that should receive run reports.
- 5Send one real test webhook for a safe workflow run.
Questions about this workflow
Should this approve every fork run?
No. State the exact trusted repository and run criteria in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Spotify to GitHub. A trigger fires from one place; an action lands in another.
Spotify triggers
GitHub actions
New Device Added
Triggers when a new device is added.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Spotify Playlist Item Change
Triggers when songs are added to or removed from a Spotify playlist.
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.
New Playlist Created or Deleted
Triggers when a new playlist is created or deleted.
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 Spotify and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.