Skip to content
HookDeploy

ZAPIER INTEGRATION

Connect webhooks to thousands of apps with Zapier

Trigger any Zap the instant a webhook is captured, forwarded, or fails. Route Stripe payments to your CRM, post GitHub events to Slack, and automate anything — without writing code.

Get started free Add via HookDeploy dashboard ↗
The Zapier integration is currently in beta. Add it to your Zapier account via the Integrations page in your HookDeploy dashboard.

How it works

Three steps to connect

  1. 1

    Connect your API key

    Add your HookDeploy API key (`hd_live_xxxx`) to Zapier. The connection validates against your org immediately.

  2. 2

    Choose a trigger

    Select which endpoint to watch and which event to fire on. Use New Webhook Received for real-time capture events.

  3. 3

    Pick your action

    Map any field from the webhook payload — body, headers, or query params — to actions across thousands of Zapier apps.

Workflow path · trigger → payload map → action

Source

Stripe / GitHub / any

HookDeploy

Capture + inspect

Zap trigger

New Webhook Received

Any app

Slack / Gmail / Notion

Modules

Triggers and actions

Triggers

  • New Webhook Received

    Fires in real time when any webhook is captured on your endpoint. Delivers the full decrypted body, headers, query params, source IP, and timestamp.

  • Forwarding Succeeded

    Fires when HookDeploy successfully delivers a webhook to a destination (2xx response). Includes response time and destination details.

  • Forwarding Failed

    Fires when a delivery attempt fails. Includes error details and the destination that failed — use to alert or auto-replay.

  • New Incident

    Fires when HookDeploy opens a new incident from correlated forward failures. Includes likely cause, failure count, and scope.

  • Incident Investigating

    Fires when an incident is marked Investigating — use to sync triage status into other tools.

  • Incident Resolved

    Fires when an incident is marked Resolved.

Actions

Create Endpoint

Programmatically create a new webhook endpoint from any Zap.

Pause Endpoint

Pause webhook capture on an endpoint from your automation.

Resume Endpoint

Resume a paused endpoint without opening the dashboard.

Invite Member

Invite a new team member to your org. Requires Admin or Super Admin API key.

Deactivate Member

Revoke a member's access immediately. Requires Admin or Super Admin API key.

Reactivate Member

Restore a deactivated member's access. Requires Admin or Super Admin API key.

List Endpoints

Return all endpoints in your org. Use in multi-step Zaps to select a target endpoint dynamically.

List Requests

Fetch recent requests on an endpoint. Returns method, size, source IP, and timestamp.

Get Request

Retrieve a single captured webhook with its full decrypted payload, headers, and query parameters.

Replay Request

Re-deliver a captured webhook to any target URL. Returns status code and response time.

Update Incident Status

Mark an incident Investigating or Resolved from another tool in your Zap.

Replay Incident

Queue a paced replay of unreplayed failures for an incident. Requires Starter or above.

Create Destination

Create a saved destination in your library. Optionally attach it to an endpoint on create.

Examples

Example scenarios

Stripe payment → Google Sheets

New Webhook Received → Filter: body.type = payment_intent.succeeded → Google Sheets: Create Row

Map `body.data.object.amount` and `body.data.object.currency` to spreadsheet columns for real-time revenue tracking.

Delivery failure → PagerDuty alert

Forwarding Failed → PagerDuty: Create Incident

Page your on-call engineer the moment a critical webhook delivery fails, with the endpoint name and failure reason mapped directly.

New GitHub push → Slack notification

New Webhook Received → Filter: headers.x-github-event = push → Slack: Send Message

Post a message to your engineering channel with the repo name and commit author pulled directly from `body.repository.full_name`.

Payload format

What Zapier receives

Capture triggers include body, headers, query params, and HookDeploy metadata. Forwarding success and failure triggers include destination and result fields instead of the original request body.


{
  "hookdeploy": {
    "request_id": "uuid",
    "endpoint_slug": "k3p9xabc7m2q8r4t",
    "captured_at": "2026-07-04T19:00:00Z",
    "method": "POST",
    "body_size_bytes": 563
  },
  "headers": {
    "content-type": "application/json",
    "x-stripe-signature": "t=..."
  },
  "body": {
    "type": "payment_intent.succeeded",
    "data": { "object": { "amount": 4200 } }
  },
  "query": {}
}

FAQ

Common questions

How do I add HookDeploy to Zapier? +
The Zapier integration is currently in beta. Go to Integrations in your HookDeploy dashboard to find your personal invite link — click it to add HookDeploy directly to your Zapier account.
Is this a real-time trigger or does Zapier poll? +
Real-time. HookDeploy uses Zapier's REST Hook pattern — your Zap fires within 1–2 seconds of a webhook being captured, not on a polling interval.
Is the webhook body decrypted before Zapier receives it? +
Yes. HookDeploy decrypts the AES-256-GCM payload server-side before delivering to Zapier. Your Zap receives plaintext fields.
Can I use the same API key for Zapier and the REST API? +
Yes — HookDeploy API keys (`hd_live_xxxx`) work for both the public REST API and the Zapier integration. Create a dedicated key for each integration in your dashboard under API Keys.

Ready to automate?

Create an endpoint, grab your API key, and add the Zapier integration from your dashboard.

Get started free Add via HookDeploy dashboard ↗