GitHub Trigger
Triggers a workflow when events occur in a GitHub repository. The webhook is automatically registered with GitHub when the workflow is published — no manual setup required.
Requires a GitHub connection with a token that has the admin:repo_hook scope.
Configuration
| Field | Description | Notes |
|---|---|---|
| Connection | GitHub connection to use. The repository to watch is defined on the connection. | Required |
| Events | Which events to listen for | Required. Multiple selection |
Supported Events
| Event | Description |
|---|---|
push | Push to any branch |
pull_request | Pull request opened, closed, merged, etc. |
issues | Issue opened, closed, edited, etc. |
issue_comment | Comment on an issue or PR |
create | Branch or tag created |
delete | Branch or tag deleted |
release | Release published, created, etc. |
workflow_run | GitHub Actions workflow completed |
star | Repository starred |
fork | Repository forked |
Output
The trigger passes the full GitHub webhook payload to downstream nodes. Key fields include:
| Field | Description |
|---|---|
body.action | Event action (e.g., opened, closed, created) |
body.sender | GitHub user who triggered the event |
body.repository | Repository details |
headers.X-GitHub-Event | Event type name |
How It Works
- You pick the GitHub connection (which carries the repository) and select which events to listen for
- The webhook is auto-registered on that repository when the connection is created, and shared by every workflow whose GitHub Trigger uses this connection
- GitHub sends every event for the repository to a single connection-scoped webhook URL; each trigger node filters by its configured event list
- Deleting the connection unregisters the webhook in GitHub
Required Token Scope
Your GitHub personal access token must include the admin:repo_hook scope to create and manage webhooks. Without this scope, webhook registration will fail silently and the trigger won't receive events.