Webhook Trigger

The Webhook trigger provides a dedicated URL that receives HTTP POST requests from external services. When a request arrives, the workflow starts automatically with the webhook payload as input.

Overview

Supported Providers

Zelaxy supports webhook triggers from the following services. Each provider has its own output schema — see the detailed sections below.

How It Works

1. Activate the workflow — a unique webhook URL is generated
2. Copy the URL and register it in the external service's webhook settings
3. When the service sends an event, the workflow triggers
4. Service-specific webhooks (Slack, GitHub, Telegram, etc.) flatten event data to convenient top-level properties — e.g., {{Webhook 1.event.text}}, {{Webhook 1.message.text}}
5. Generic webhooks store the raw request body under webhook.data.payload — access fields via {{Webhook 1.webhook.data.payload.fieldName}}

Block name normalization: Block names are case-insensitive and spaces are removed. {{Webhook 1.field}}, {{webhook1.field}}, and {{WEBHOOK1.field}} all resolve to the same block.

Universal Raw Data Access (All Providers)

Every webhook trigger (regardless of provider) also stores the complete raw HTTP request under webhook.data. This provides a fallback when you need fields not covered by the provider-specific outputs:

Signature verification

When you configure a signing secret for a supported provider, Zelaxy verifies every incoming delivery and rejects requests whose signature does not match (HTTP 401) — so a caller who merely knows the URL cannot fire the workflow. Verification is enforced for GitHub, Slack, Linear, Asana, GitLab, Typeform, Sentry, Calendly, PagerDuty, Vercel, Zoom, Clerk, Resend, Cal.com, Twilio, and the Atlassian/support integrations Jira, Confluence, Notion, Intercom, and Zendesk.

The scheme matches each provider's documented signing exactly — for example Intercom is HMAC-SHA1 over the body (sha1= in X-Hub-Signature), Notion and Jira/Confluence are HMAC-SHA256 hex (sha256=), and Zendesk is base64 HMAC-SHA256 over timestamp + body with a 5-minute freshness window. Notion's initial unsigned verification handshake is acknowledged automatically. Providers with no documented signing scheme are intentionally left unverified rather than guessing a scheme that would silently reject genuine deliveries — use the generic webhook's bearer token or IP allowlist for those.

Gmail

Triggers when new emails are received in a connected Gmail account. Requires OAuth with Google.

Configuration

Outputs

Sample Payload

{
  "email": {
    "id": "18e0ffabd5b5a0f4",
    "threadId": "18e0ffabd5b5a0f4",
    "subject": "Monthly Report - April 2025",
    "from": "sender@example.com",
    "to": "recipient@example.com",
    "cc": "team@example.com",
    "date": "2025-05-10T10:15:23.000Z",
    "bodyText": "Hello,\n\nPlease find attached the monthly report.\n\nBest regards",
    "bodyHtml": "<div><p>Hello,</p><p>Please find attached the monthly report.</p></div>",
    "labels": ["INBOX", "IMPORTANT"],
    "hasAttachments": true,
    "attachments": [
      { "filename": "report-april-2025.pdf", "mimeType": "application/pdf", "size": 2048576 }
    ]
  },
  "timestamp": "2025-05-10T10:15:30.123Z"
}

Usage Example

Reference in downstream blocks: {{Webhook 1.email.subject}}, {{Webhook 1.email.from}}, {{Webhook 1.email.bodyText}}

Outlook

Triggers when new emails are received in a connected Outlook/Microsoft 365 account. Requires OAuth with Microsoft.

Configuration

Outputs

Sample Payload

{
  "email": {
    "id": "AAMkADg1OWUyZjg4LWJkNGYtNDFhYy04OGVjLWVkM2VhY2YzYTcwZg...",
    "conversationId": "AAQkADg1OWUyZjg4LWJkNGYtNDFhYy04OGVjLWVkM2VhY2YzYTcwZg...",
    "subject": "Quarterly Business Review - Q1 2025",
    "from": "manager@company.com",
    "to": "team@company.com",
    "cc": "stakeholders@company.com",
    "date": "2025-05-10T14:30:00Z",
    "bodyText": "Hi Team,\n\nPlease find attached the Q1 2025 business review...",
    "bodyHtml": "<div><p>Hi Team,</p><p>Please find attached the Q1 review...</p></div>",
    "hasAttachments": true,
    "isRead": false,
    "folderId": "AQMkADg1OWUyZjg4LWJkNGYtNDFhYy04OGVjAC4AAAJzE3bU",
    "messageId": "AAMkADg1OWUyZjg4...",
    "threadId": "AAQkADg1OWUyZjg4..."
  },
  "timestamp": "2025-05-10T14:30:15.123Z"
}

Usage Example

Reference in downstream blocks: {{Webhook 1.email.subject}}, {{Webhook 1.email.from}}, {{Webhook 1.email.isRead}}

Slack

Triggers on Slack events like app mentions, messages, and reactions. Requires a Slack app signing secret.

Configuration

Outputs

Sample Payload

{
  "type": "event_callback",
  "event": {
    "type": "app_mention",
    "channel": "C0123456789",
    "user": "U0123456789",
    "text": "<@U0BOTUSER123> Hello from Slack!",
    "ts": "1234567890.123456",
    "channel_type": "channel"
  },
  "team_id": "T0123456789",
  "event_id": "Ev0123456789",
  "event_time": 1234567890
}

Usage Example

Reference in downstream blocks: {{Webhook 1.event.text}}, {{Webhook 1.event.user_name}}, {{Webhook 1.event.channel_name}}

GitHub

Triggers on GitHub events like push, pull requests, issues, and more. Supports webhook secret for signature verification.

Configuration

Outputs

Sample Payload (Pull Request)

{
  "action": "opened",
  "number": 1,
  "pull_request": {
    "id": 1, "number": 1, "state": "open", "title": "Update README",
    "user": { "login": "octocat", "id": 1 },
    "body": "This is a simple change to pull into main.",
    "head": { "ref": "feature-branch", "sha": "abc123" },
    "base": { "ref": "main", "sha": "def456" }
  },
  "repository": {
    "id": 35129377, "name": "public-repo", "full_name": "octocat/public-repo",
    "owner": { "login": "octocat", "id": 6752317 }
  },
  "sender": { "login": "octocat", "id": 6752317 }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.action}}, {{Webhook 1.repository.full_name}}, {{Webhook 1.sender.login}}

Telegram

Triggers on messages sent to a Telegram bot. Requires a bot token from BotFather.

Configuration

Outputs

Sample Payload

{
  "update_id": 123456789,
  "message": {
    "message_id": 123,
    "from": {
      "id": 987654321, "is_bot": false, "first_name": "John",
      "last_name": "Doe", "username": "johndoe"
    },
    "chat": {
      "id": 987654321, "first_name": "John", "last_name": "Doe",
      "username": "johndoe", "type": "private"
    },
    "date": 1234567890,
    "text": "Hello from Telegram!"
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.message.text}}, {{Webhook 1.message.from_username}}, {{Webhook 1.message.chat_id}}

WhatsApp

Triggers on incoming WhatsApp messages via the Business Platform. Requires a verification token.

Configuration

Outputs

Sample Payload

{
  "object": "whatsapp_business_account",
  "entry": [{
    "id": "1234567890123456",
    "changes": [{
      "value": {
        "messaging_product": "whatsapp",
        "metadata": {
          "display_phone_number": "15551234567",
          "phone_number_id": "1234567890123456"
        },
        "contacts": [{ "profile": { "name": "John Doe" }, "wa_id": "15555551234" }],
        "messages": [{
          "from": "15555551234",
          "id": "wamid.HBgNMTU1NTU1NTEyMzQVAgASGBQz...",
          "timestamp": "1234567890",
          "text": { "body": "Hello from WhatsApp!" },
          "type": "text"
        }]
      },
      "field": "messages"
    }]
  }]
}

Usage Example

Reference in downstream blocks: {{Webhook 1.text}}, {{Webhook 1.from}}, {{Webhook 1.messageId}}

Stripe

Triggers on Stripe events like successful payments, subscription changes, and more. Events are selected in the Stripe dashboard.

Configuration

No additional configuration needed — configure event types in your Stripe dashboard.

Outputs

Sample Payload

{
  "id": "evt_1234567890",
  "type": "charge.succeeded",
  "created": 1641234567,
  "data": {
    "object": {
      "id": "ch_1234567890", "object": "charge", "amount": 2500,
      "currency": "usd", "description": "Sample charge", "paid": true,
      "status": "succeeded", "customer": "cus_1234567890",
      "receipt_email": "customer@example.com"
    }
  },
  "object": "event",
  "livemode": false,
  "api_version": "2020-08-27",
  "request": { "id": "req_1234567890", "idempotency_key": null }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.type}}, {{Webhook 1.data}}, {{Webhook 1.id}}

Airtable

Triggers on Airtable record changes (create, update, delete). Requires OAuth with Airtable.

Configuration

Outputs

Sample Payload

{
  "webhook": { "id": "achAbCdEfGhIjKlMn" },
  "timestamp": "2023-01-01T00:00:00.000Z",
  "base": { "id": "appXXXXXXXXXXXXXX" },
  "table": { "id": "tblXXXXXXXXXXXXXX" },
  "changedTablesById": {
    "tblXXXXXXXXXXXXXX": {
      "changedRecordsById": {
        "recXXXXXXXXXXXXXX": {
          "current": {
            "id": "recXXXXXXXXXXXXXX",
            "fields": { "Name": "Sample Record", "Status": "Active" }
          },
          "previous": {
            "id": "recXXXXXXXXXXXXXX",
            "fields": { "Name": "Sample Record", "Status": "Inactive" }
          }
        }
      }
    }
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.record_id}}, {{Webhook 1.record_data}}

Microsoft Teams

Triggers on Microsoft Teams events like messages and mentions via an outgoing webhook.

Configuration

Outputs

Sample Payload

{
  "type": "message",
  "id": "1234567890",
  "timestamp": "2023-01-01T00:00:00.000Z",
  "localTimestamp": "2023-01-01T00:00:00.000Z",
  "serviceUrl": "https://smba.trafficmanager.net/amer/",
  "channelId": "msteams",
  "from": { "id": "29:1234567890abcdef", "name": "John Doe" },
  "conversation": { "id": "19:meeting_abcdef@thread.v2" },
  "text": "Hello Zelaxy Bot!"
}

Usage Example

Reference in downstream blocks: {{Webhook 1.text}}, {{Webhook 1.from_name}}, {{Webhook 1.conversation_id}}

Generic Webhook

Universal HTTP endpoint that accepts requests from any source. No provider-specific validation.

See the dedicated Generic Webhook page for full details, including comprehensive data access examples.

Outputs

For generic webhooks, the raw HTTP request is stored under the webhook.data namespace:

Usage Example

If the external service sends:

{
  "event": "message.received",
  "data": {
    "provider_message_id": "msg_abc123",
    "content": "Hello world"
  }
}

Reference in downstream blocks:

• {{Webhook 1.webhook.data.payload}} — full body
• {{Webhook 1.webhook.data.payload.event}} — "message.received"
• {{Webhook 1.webhook.data.payload.data.provider_message_id}} — "msg_abc123"
• {{Webhook 1.webhook.data.payload.data.content}} — "Hello world"
• {{Webhook 1.webhook.data.headers}} — request headers
• {{Webhook 1.webhook.data.method}} — "POST"

GitLab

Triggers on GitLab events like pushes, merge requests, issues, pipelines, and comments. The secret token is verified on every delivery.

Configuration

Outputs

Sample Payload (Push)

{
  "object_kind": "push",
  "event_name": "push",
  "ref": "refs/heads/main",
  "checkout_sha": "da1560886d4f094c3e6c9ef40349f7d38b5d27d7",
  "user_name": "John Smith",
  "user_username": "jsmith",
  "project_id": 15,
  "project": {
    "name": "Diaspora", "path_with_namespace": "mike/diaspora",
    "web_url": "http://example.com/mike/diaspora", "default_branch": "main"
  },
  "commits": [
    { "id": "da15608", "message": "fix: typos in readme", "author": { "name": "John Smith" } }
  ],
  "total_commits_count": 1
}

Usage Example

Reference in downstream blocks: {{Webhook 1.object_kind}}, {{Webhook 1.branch}}, {{Webhook 1.commit_message}}

Typeform

Triggers when a form receives a new submission. Requires a Typeform PRO or PRO+ account. The webhook secret is verified on every delivery.

Configuration

Outputs

Sample Payload

{
  "event_id": "01HZ8X2Q9Y3M4N5P6R7S8T9V0W",
  "event_type": "form_response",
  "form_response": {
    "form_id": "lT4Z3j",
    "token": "a3a12ec67a1365927098a606107fac15",
    "submitted_at": "2024-01-15T13:14:15Z",
    "definition": {
      "id": "lT4Z3j", "title": "Customer Feedback",
      "fields": [{ "id": "DlXFaesGBpoF", "type": "email", "title": "What is your email?" }]
    },
    "answers": [
      { "type": "email", "email": "ada@example.com", "field": { "id": "DlXFaesGBpoF", "type": "email" } }
    ],
    "hidden": {}
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.form_title}}, {{Webhook 1.fields.What is your email?}}, {{Webhook 1.answer_count}}

Sentry

Triggers on Sentry issues, error events, and alert rules. The client secret is verified on every delivery.

Configuration

Outputs

Sample Payload (Issue Created)

{
  "action": "created",
  "data": {
    "issue": {
      "id": "1234567890", "shortId": "MY-PROJECT-1",
      "title": "TypeError: Cannot read property 'id' of undefined",
      "culprit": "app/routes/checkout in handler",
      "status": "unresolved", "level": "error", "count": "3", "userCount": 2,
      "permalink": "https://sentry.io/organizations/my-org/issues/1234567890/",
      "project": { "slug": "my-project" }
    }
  },
  "actor": { "type": "application", "id": "sentry", "name": "Sentry" }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.issue_title}}, {{Webhook 1.level}}, {{Webhook 1.issue_url}}

Calendly

Triggers when an invitee books or cancels a meeting, or submits a routing form. The signing key is verified on every delivery.

Configuration

Outputs

Sample Payload (Invitee Created)

{
  "event": "invitee.created",
  "created_at": "2024-01-15T13:14:15.000000Z",
  "payload": {
    "email": "ada@example.com", "name": "Ada Lovelace",
    "status": "active", "timezone": "America/New_York", "rescheduled": false,
    "questions_and_answers": [
      { "question": "What would you like to discuss?", "answer": "Pricing", "position": 0 }
    ],
    "scheduled_event": {
      "name": "30 Minute Meeting", "status": "active",
      "start_time": "2024-01-20T15:00:00.000000Z",
      "end_time": "2024-01-20T15:30:00.000000Z",
      "location": { "type": "google_conference", "join_url": "https://meet.google.com/abc-defg-hij" }
    }
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.invitee_email}}, {{Webhook 1.start_time}}, {{Webhook 1.join_url}}

PagerDuty

Triggers on incident lifecycle events — triggered, acknowledged, escalated, reassigned, resolved. The webhook secret is verified on every delivery.

Configuration

Outputs

Sample Payload (Incident Triggered)

{
  "event": {
    "id": "01DPXQZG4Z3ZBQ0N2T0Q9W8XYZ",
    "event_type": "incident.triggered",
    "occurred_at": "2024-01-15T13:14:15.000Z",
    "agent": { "summary": "Ada Lovelace" },
    "data": {
      "id": "PABCDEF", "number": 1234, "title": "Checkout API returning 500s",
      "status": "triggered", "urgency": "high",
      "html_url": "https://acme.pagerduty.com/incidents/PABCDEF",
      "service": { "id": "PSVC123", "summary": "Checkout API" },
      "assignees": [{ "id": "PXXXXXX", "summary": "Ada Lovelace" }]
    }
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.title}}, {{Webhook 1.urgency}}, {{Webhook 1.assignee_names}}

Vercel

Triggers on deployment and project events. The webhook secret is verified on every delivery.

Configuration

Outputs

Sample Payload (Deployment Ready)

{
  "id": "uev_1234567890abcdef",
  "type": "deployment.ready",
  "createdAt": 1705324455000,
  "region": "iad1",
  "payload": {
    "team": { "id": "team_abc123" },
    "project": { "id": "prj_abc123", "name": "zelaxy-web" },
    "deployment": {
      "id": "dpl_abc123", "name": "zelaxy-web",
      "url": "zelaxy-web-abc123.vercel.app", "target": "production",
      "meta": {
        "githubCommitRef": "main",
        "githubCommitSha": "da1560886d4f094c3e6c9ef40349f7d38b5d27d7",
        "githubCommitMessage": "fix: correct minor typos in readme"
      }
    }
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.deployment_url}}, {{Webhook 1.git_branch}}

Zoom

Triggers on Zoom meeting, participant, and recording events. The Secret Token is required — Zoom validates the endpoint by calling it before the webhook can be enabled.

Configuration

Outputs

Sample Payload (Meeting Started)

{
  "event": "meeting.started",
  "event_ts": 1705324455000,
  "payload": {
    "account_id": "abc123",
    "object": {
      "id": "81234567890", "uuid": "aBcDeFgHiJk==",
      "topic": "Weekly Standup", "host_id": "xyz789",
      "start_time": "2024-01-15T13:00:00Z", "duration": 30
    }
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.topic}}, {{Webhook 1.participant_name}}

Clerk

Triggers on Clerk user, session, and organization events. Clerk signs deliveries with Svix.

Configuration

Outputs

Sample Payload (User Created)

{
  "type": "user.created",
  "object": "event",
  "data": {
    "id": "user_2abc123",
    "first_name": "Ada", "last_name": "Lovelace", "username": "ada",
    "primary_email_address_id": "idn_2abc",
    "email_addresses": [{ "id": "idn_2abc", "email_address": "ada@example.com" }],
    "created_at": 1705324455000
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.email}}, {{Webhook 1.full_name}}

Cal.com

Triggers on Cal.com booking events — created, rescheduled, cancelled, and meeting ended.

Configuration

Outputs

Sample Payload (Booking Created)

{
  "triggerEvent": "BOOKING_CREATED",
  "createdAt": "2024-01-15T13:14:15.000Z",
  "payload": {
    "bookingId": 123456, "uid": "abc123xyz",
    "title": "30 Min Meeting between Ada and Alan",
    "startTime": "2024-01-20T15:00:00Z", "endTime": "2024-01-20T15:30:00Z",
    "status": "ACCEPTED",
    "organizer": { "name": "Ada Lovelace", "email": "ada@example.com" },
    "attendees": [{ "name": "Alan Turing", "email": "alan@example.com" }],
    "responses": { "name": { "label": "your_name", "value": "Alan Turing" } }
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.title}}, {{Webhook 1.attendee_email}}, {{Webhook 1.answers.name}}

Resend

Triggers on Resend email delivery events. Resend signs deliveries with Svix.

Configuration

Outputs

Sample Payload (Email Delivered)

{
  "type": "email.delivered",
  "created_at": "2024-01-15T13:14:15.000Z",
  "data": {
    "email_id": "4ef9a417-02e9-4d39-ad75-9611e0fcc33c",
    "from": "noreply@zelaxy.in",
    "to": ["ada@example.com"],
    "subject": "Welcome to Zelaxy"
  }
}

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.to_email}}, {{Webhook 1.subject}}

Twilio SMS

Triggers when your Twilio number receives an SMS or MMS.

Configuration

Outputs

Sample Payload

{
  "MessageSid": "SMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "AccountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "From": "+15551234567",
  "To": "+15559876543",
  "Body": "Hello from Twilio",
  "NumMedia": "0",
  "FromCity": "SAN FRANCISCO",
  "SmsStatus": "received"
}

Usage Example

Reference in downstream blocks: {{Webhook 1.from}}, {{Webhook 1.body}}, {{Webhook 1.media}}

Twilio Voice

Triggers when your Twilio number receives a call, or when a call status or recording changes.

Configuration

Outputs

Sample Payload

{
  "CallSid": "CAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "AccountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "From": "+15551234567",
  "To": "+15559876543",
  "CallStatus": "ringing",
  "Direction": "inbound"
}

Usage Example

Reference in downstream blocks: {{Webhook 1.from}}, {{Webhook 1.call_status}}, {{Webhook 1.recording_url}}

Attio

Triggers on records, notes, tasks, and lists changing.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.webhook_id}}, {{Webhook 1.record_id}}

Azure DevOps

Triggers on builds, work items, and pull requests.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.message}}, {{Webhook 1.build_number}}

Gong

Triggers on calls being processed and transcripts becoming ready.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.call_id}}, {{Webhook 1.call_title}}

Greenhouse

Triggers on candidates being hired, rejected, or changing stage.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.candidate_id}}, {{Webhook 1.candidate_name}}

Ashby

Triggers on applications submitted and candidates changing stage.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.candidate_id}}, {{Webhook 1.candidate_name}}

incident.io

Triggers on incidents being created, updated, or resolved.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.incident_id}}, {{Webhook 1.incident_name}}

Rootly

Triggers on incidents being created, mitigated, or resolved.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.incident_id}}, {{Webhook 1.incident_title}}

RevenueCat

Triggers on purchases, renewals, cancellations, and expirations.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.event_id}}, {{Webhook 1.app_user_id}}

Loops

Triggers on email sent, delivered, opened, clicked, and bounced.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.email}}, {{Webhook 1.contact_id}}

Fathom

Triggers when a meeting recording, summary, or transcript is ready.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.meeting_id}}, {{Webhook 1.meeting_title}}

Grain

Triggers on recordings completing and highlights being created.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.recording_id}}, {{Webhook 1.recording_title}}

Instantly

Triggers on campaign replies, opens, clicks, and bounces.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.campaign_id}}, {{Webhook 1.campaign_name}}

lemlist

Triggers on campaign replies, opens, clicks, and bounces.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.campaign_id}}, {{Webhook 1.campaign_name}}

Linq

Triggers on messages being delivered, failing, or replied to.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.message_id}}, {{Webhook 1.status}}

Circleback

Triggers when a meeting completes and notes or action items are ready.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.meeting_id}}, {{Webhook 1.meeting_name}}

EmailBison

Triggers on replies received and sending accounts disconnecting.

Configuration

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.campaign_id}}, {{Webhook 1.campaign_name}}

Sendblue

Triggers on iMessage/SMS messages received or status changing.

Configuration

This provider does not sign or authenticate its webhooks. Treat the webhook URL as the secret — it is unguessable, but anyone who has it can start your workflow. Use the provider's IP allowlist if it offers one.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.event_type}}, {{Webhook 1.message_handle}}, {{Webhook 1.from_number}}

RSS

Triggers once per new item published to an RSS or Atom feed.

Configuration

Outputs

How it behaves

• Runs once per new item, oldest first, so a burst of posts arrives in publication order.
• Items are identified by their guid (falling back to id, then link, then title), so editing a title or link in place does not re-trigger.
• At most 10 items fire per poll of a feed, so a feed that publishes a large backlog cannot flood your workflow.
• Recent item ids are remembered, so an item that briefly drops out of the feed window and comes back is not treated as new.

Sample Payload

{
  "feedUrl": "https://example.com/feed.xml",
  "item": {
    "id": "https://example.com/posts/hello-world",
    "title": "Hello world",
    "link": "https://example.com/posts/hello-world",
    "pubDate": "Mon, 15 Jan 2024 13:14:15 GMT",
    "description": "Our first post."
  }
}

Usage Example

Reference in downstream blocks: {{RSS 1.title}}, {{RSS 1.link}}, {{RSS 1.description}}

Google Forms

Triggers when a form receives a new response.

Configuration

Setup

1. Open your form, click the three-dot menu > Apps Script.
2. Paste the script below, replacing WEBHOOK_URL and SHARED_SECRET with the values from the trigger.
3. In the Apps Script editor open Triggers (clock icon) > Add Trigger: function onFormSubmit, event source From form, event type On form submit.
4. Authorise the script when prompted, then submit a test response.

function onFormSubmit(e) {
  const WEBHOOK_URL = "<your webhook URL>";
  const SHARED_SECRET = "<your shared secret>";

  const formResponse = e.response;
  const itemResponses = formResponse.getItemResponses();

  const answers = {};
  for (var i = 0; i < itemResponses.length; i++) {
    answers[itemResponses[i].getItem().getTitle()] = itemResponses[i].getResponse();
  }

  const payload = {
    provider: "google_forms",
    formId: e.source.getId(),
    responseId: formResponse.getId(),
    createTime: formResponse.getTimestamp().toISOString(),
    lastSubmittedTime: formResponse.getTimestamp().toISOString(),
    answers: answers
  };

  UrlFetchApp.fetch(WEBHOOK_URL, {
    method: "post",
    contentType: "application/json",
    headers: { "Authorization": "Bearer " + SHARED_SECRET },
    payload: JSON.stringify(payload),
    muteHttpExceptions: true
  });
}

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.form_id}}, {{Webhook 1.answers.What is your email?}}, {{Webhook 1.answer_count}}

IMAP

Triggers when a new email arrives in a mailbox. Works with any IMAP provider — Gmail, Outlook, Yahoo, Fastmail, or a self-hosted server.

Configuration

Outputs

How it behaves

• Runs once per new email, oldest first, capped at 25 per poll so a backlog cannot flood a workflow.
• Tracks position by IMAP UID. If the server changes UIDVALIDITY — which invalidates every UID it ever issued — Zelaxy detects it, resyncs to the current end of the mailbox, and does not replay the mailbox.
• If a workflow run fails to dispatch, the cursor is not advanced past it, so it is retried on the next poll rather than lost.
• Dropped connections and throttling are treated as normal and retried on the next poll.

Sample Payload

{
  "mailbox": "INBOX",
  "email": {
    "uid": 1042,
    "messageId": "<CAF=abc123@mail.example.com>",
    "subject": "Invoice #4102",
    "from": { "address": "billing@vendor.com", "name": "Vendor Billing" },
    "to": ["ada@example.com"],
    "date": "2024-01-15T13:14:15.000Z",
    "hasAttachments": true
  }
}

Usage Example

Reference in downstream blocks: {{IMAP 1.subject}}, {{IMAP 1.from}}, {{IMAP 1.body_text}}

Jira Service Management

Triggers when a service desk request is created, updated, commented on, or resolved.

Configuration

Setup

1. In Jira, go to Settings > System > WebHooks and click Create a WebHook.
2. Paste the Webhook URL into the URL field and the Webhook Secret into the Secret field.
3. Tick the Issue events you want (created, updated, deleted) and Comment > created for comment events.
4. Optionally add a JQL filter such as project = SUP so only your service desk fires the workflow.

Outputs

Usage Example

Reference in downstream blocks: {{Webhook 1.issue_key}}, {{Webhook 1.summary}}, {{Webhook 1.comment_body}}

Data Access Reference

Variable Syntax

All webhook data is accessed using the {{BlockName.path.to.field}} template syntax inside any connected downstream block (Agent, Function, API, Condition, etc.).

{{Webhook 1.path.to.field}}

• Block name = the label on the canvas (default: Webhook 1)
• Path = dot-separated property path into the block output
• Block names are normalized: case-insensitive, spaces removed (Webhook 1 = webhook1)

Provider-Specific vs Raw Data Access

Nested Field Access

Use dots to traverse nested objects:

{{Webhook 1.webhook.data.payload.data.provider_message_id}}

This resolves the path: output → webhook → data → payload → data → provider_message_id

Array Access

Use bracket notation to access array elements:

{{Webhook 1.webhook.data.payload.items[0].name}}

Common Generic Webhook Patterns

Security

• Always set a webhook secret — validates that requests come from the actual service
• HTTPS only — all webhook URLs use HTTPS
• Signature verification — Zelaxy validates webhook signatures automatically for supported providers

Tips

• Each workflow has a unique URL — don't share it publicly
• Test with curl: curl -X POST https://your-webhook-url -H "Content-Type: application/json" -d '{"test": true}'
• Retry handling — some services retry failed webhooks; ensure your workflow is idempotent