TriggerGitHubReal-timeUpdated May 2026

How do I trigger on GitHub events (push, PR, issue, release)?

Short answer: Drop the "GitHub → New GitHub Event" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in GitHub, not on a polling schedule.

Use this trigger All 1 GitHub triggers

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

New GitHub Event

When the matching event happens

githubgithub webhookpushpull requestissuereleaseforkstar

What this trigger returns

for the curious

You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "raw": {
    "ref": "refs/heads/main",
    "after": "def5678",
    "repository": {
      "full_name": "octocat/hello-world"
    }
  },
  "ref": "refs/heads/main",
  "pusher_name": "octocat",
  "sender_login": "octocat",
  "head_commit_id": "def5678",
  "repository_url": "https://github.com/octocat/hello-world",
  "head_commit_message": "Fix login bug",
  "repository_full_name": "octocat/hello-world"
}

Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

Field	Type	Example
raw	object	{ … }
raw.ref	string	"refs/heads/main"
raw.after	string	"def5678"
raw.repository	object	{ … }
raw.repository.full_name	string	"octocat/hello-world"
ref	string	"refs/heads/main"
pusher_name	string	"octocat"
sender_login	string	"octocat"
head_commit_id	string	"def5678"
repository_url	string	"https://github.com/octocat/hello-world"
head_commit_message	string	"Fix login bug"
repository_full_name	string	"octocat/hello-world"

Pairs with

Drop these actions after New GitHub Event.

Add Labels to Message

Gmail · Email

Raw API Request

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about New GitHub Event.

How does the New GitHub Event trigger work in GitHub?

Fires when the selected events occur on a GitHub repository. One webhook is registered per workflow on the chosen repo, with the events list filtered server-side by GitHub. Pick from push, pull_request, issues, release, deployment, and many others.

Is the New GitHub Event trigger real-time?

Yes. New GitHub Event uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in GitHub.

What data does New GitHub Event return?

The full event payload from GitHub. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.

Can I filter New GitHub Event so only some events start a workflow?

Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.

Do I need GitHub admin permissions to use New GitHub Event?

For most GitHub accounts a standard user can authorize the trigger. Some GitHub plans require an admin to enable third-party webhooks. Check GitHub's docs if the trigger fails to register.

Build a workflow on this trigger.

One trigger. 23+ downstream actions. Zero glue.

Try for free Request a demo