Skip to content
Notis

Approve a GitHub fork PR workflow run from an incoming signal

Fork pull requests wait for a manual approval on their workflow run, and that click always sits until you notice it. When your Jira approval gate fires a webhook, Notis approves the pending run on GitHub so contributor checks flow.

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

Workflow runs from fork pull requests sit paused waiting for approval, blocking external contributors while the click waits on you.

  • Contributor checks start as soon as your approval gate clears
  • No more paused runs waiting on a click you did not see
  • External contributors get a faster, less confusing experience

Setup

Build it in a few focused steps.

  • 1Connect GitHub to Notis once from the portal.
  • 2Open Automations in the portal and choose New Automation.
  • 3Write the instruction: when this webhook fires, approve the pending GitHub workflow run for the referenced fork pull request.
  • 4Select the incoming webhook trigger and pick a channel for run reports.
  • 5Send a test webhook and confirm the workflow run is approved on GitHub.

Questions about this workflow

When does the webhook come from?

From any tool or backend you point at Notis, including a Jira gate or a custom approval service.

Which runs can it approve?

Workflow runs from a forked repository's pull request that require manual approval.

Do I need a Jira event for this?

No. This uses an incoming webhook, so it starts whenever your system posts the request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to GitHub. A trigger fires from one place; an action lands in another.

Jira triggers

GitHub actions

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Jira 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.