ZelaxyDocs
Triggers

Triggers

Automatically start workflows from webhooks, schedules, and external events

Triggers

Triggers start workflows automatically — no manual execution needed. Configure webhooks to respond to external events, schedules for recurring tasks, or generic webhooks for custom integrations.

How Triggers Work

  1. Configure a trigger on your workflow's Starter block
  2. Activate the workflow — this registers the trigger endpoint
  3. External events hit the trigger and start the workflow automatically

Trigger data is available in your workflow via {{starter.input}} (payload body) and {{starter.trigger}} (trigger metadata like headers).

Trigger Types

TypeDescriptionUse Case
WebhookDedicated URL per serviceService-specific integrations
Generic WebhookUniversal HTTP endpointAny service that can send POST requests
ScheduleCron-based time triggersRecurring tasks (hourly reports, daily syncs)

Supported Webhook Providers

ProviderAuthOutputs
GmailOAuthEmail subject, from, to, body, attachments
OutlookOAuthEmail subject, from, to, body, folders, read status
SlackSigning SecretEvent type, channel, user, message text
GitHubWebhook SecretPush, PR, issues — commits, repo, sender
TelegramBot TokenMessage text, sender, chat info
WhatsAppVerification TokenMessage text, sender phone, message ID
StripeEvent type, payment data, customer info
AirtableOAuthRecord changes, field data, event type
Microsoft TeamsHMAC SecretMessage text, sender, channel, conversation
GenericOptionalFull payload, headers, method, query params

Example: GitHub PR Review Automation

[Starter (webhook: GitHub)] → [Agent: Review PR] → [GitHub: Comment]
  1. Configure a GitHub webhook trigger on the Starter
  2. GitHub sends a webhook when a PR is opened
  3. Agent reads the PR diff and generates a code review
  4. GitHub block posts the review as a PR comment

Tips

  • Webhooks are instant — trigger fires immediately when the event occurs
  • Schedules use cron syntax — 0 9 * * 1-5 = weekdays at 9am
  • Test triggers by sending a curl request to the webhook URL
  • Trigger data is the raw HTTP body — use a Function block to parse if needed