Configuration
Full settings reference for the GitHub webhook trigger node — all filters, access controls, and processing options explained.
All settings are optional unless noted. When a filter is not configured, no filtering of that type is applied and all matching events pass through. Events that fail any configured filter are silently discarded — the workflow is not started.
Security Settings
| Setting | Type | Description |
|---|---|---|
WebhookSecret | string | HMAC SHA256 webhook secret. When set, BizFirst verifies the x-hub-signature-256 header on every incoming request. Events with missing or invalid signatures are rejected before any workflow starts. Strongly recommended for production. |
Event Type Filters
| Setting | Type | Description |
|---|---|---|
AllowedEventTypes | string | Comma-separated list of event types to process. Allowed values: push, pull_request, issues, release, workflow_run. If not set, all supported event types are accepted. Example: push,pull_request. |
Repository and Organisation Filters
| Setting | Type | Description |
|---|---|---|
AllowedRepositories | string | Comma-separated list of repositories in owner/repo format. Only events from these repositories will trigger the workflow. Example: myorg/api-service,myorg/web-app. |
AllowedOrganizations | string | Comma-separated list of GitHub organisation names. Only events from repositories belonging to these organisations are processed. |
Push Event Filters
| Setting | Type | Description |
|---|---|---|
AllowedBranches | string | Comma-separated list of branch names or patterns. Applies to push events only. Supports wildcards — for example release/* matches all release branches. Example: main,release/*,hotfix/*. |
OnlyProcessNonEmptyPushes | bool | Default: false. When true, push events with zero commits (e.g. branch deletions or tag operations with no new commits) are discarded. |
Pull Request Action Filters
| Setting | Type | Description |
|---|---|---|
AllowedPullRequestActions | string | Comma-separated list of PR actions to process. Available values: opened, synchronize, reopened, closed, edited, assigned, unassigned, labeled, unlabeled, review_requested, review_request_removed. If not set, all PR actions are accepted. |
Issue Action Filters
| Setting | Type | Description |
|---|---|---|
AllowedIssueActions | string | Comma-separated list of issue actions to process. Available values: opened, edited, deleted, transferred, pinned, unpinned, closed, reopened, assigned, unassigned, labeled, unlabeled, locked, unlocked, milestoned, demilestoned. If not set, all issue actions are accepted. |
Access Control Settings
| Setting | Type | Description |
|---|---|---|
RequireContributorAccess | bool | Default: false. When true, only events sent by users who have push (write) access to the repository are processed. Events from external contributors or bots without push access are discarded. |
RequireOwnerOrMember | bool | Default: false. When true, only events from the repository owner or organisation members are processed. Events from outside collaborators are discarded. |
Output and Deduplication Settings
| Setting | Type | Description |
|---|---|---|
IncludeFullEventObject | bool | Default: false. When true, the complete GitHub webhook JSON payload is included in the output as full_event_json, in addition to the standard parsed fields. |
EnableIdempotencyCheck | bool | Default: false. When true, BizFirst checks the X-GitHub-Delivery header to detect duplicate deliveries. If the same delivery ID has been processed before, the event is discarded without starting a workflow. Useful when GitHub retries failed deliveries. |
Registered Webhook Endpoints
Each event type has a dedicated BizFirst endpoint. Register the correct URL in your GitHub webhook settings for each event type you want to receive:
| BizFirst Endpoint | GitHub Event Type |
|---|---|
POST /webhooks/github/push | push |
POST /webhooks/github/pull-request | pull_request |
POST /webhooks/github/issues | issues |
POST /webhooks/github/releases | release |
POST /webhooks/github/workflow | workflow_run |
Multiple event types on one node: If you configure a single GitHub node to accept multiple event types, set
AllowedEventTypes to the comma-separated list and use a Switch node downstream on event_type to route each event to the correct workflow branch.