MAKE.COM INTEGRATION
Connect webhooks to Make scenarios in real time
Trigger Make.com scenarios the instant a webhook is captured. Route payloads, automate workflows, and inspect every delivery — no code required.
How it works
Three steps to connect
- 1
Connect your API key
Add your HookDeploy API key to the Make.com connection. It validates instantly against your org.
- 2
Pick a trigger
Choose which endpoint to watch and what event to fire on — new webhook, delivery success, or failure.
- 3
Build your scenario
Map fields from the webhook payload to any Make.com module. Full body, headers, and query params are available.
Source
Stripe / GitHub / any
HookDeploy
Capture + inspect
Make trigger
New Webhook Received
Your scenario
Slack / Sheets / CRM
Modules
Triggers and actions
-
New Webhook Received
Fires instantly when any webhook is captured on your endpoint. Delivers full body, headers, query params, and metadata.
-
Forwarding Succeeded
Fires when a webhook is successfully delivered to a destination (2xx response). Includes destination details and response time.
-
Forwarding Failed
Fires when a delivery attempt returns a non-2xx status or times out. Use to alert on delivery failures.
-
Create Endpoint
Create a new webhook endpoint from a scenario.
-
Pause Endpoint / Resume Endpoint
Halt or restore webhook capture on demand.
-
Replay Request
Re-deliver a captured webhook to any target URL.
-
Invite Member / Deactivate Member / Reactivate Member
Manage org members from your automation.
Get Request
Retrieve a specific captured webhook with full decrypted payload and forward results.
List Requests
Fetch recent requests on an endpoint with cursor-based pagination.
List Endpoints
Return all endpoints in your org for use in dynamic dropdowns.
Examples
Example scenarios
Stripe payment → Google Sheets row
New Webhook Received → Filter: body.type = payment_intent.succeeded → Add row to Google Sheets
Map `body.data.object.amount`, `body.data.object.currency`, and `hookdeploy.captured_at` directly to spreadsheet columns.
Delivery failure → Slack alert + replay
Forwarding Failed → Post Slack message → Wait 5 minutes → Replay Request
Alert your team immediately when a delivery fails, then automatically retry once after a delay.
GitHub push → Jira ticket
New Webhook Received → Filter: headers.x-github-event = push → Create Jira Issue
Use headers from the captured request alongside body fields — both are available as mappable variables in every Make.com module.
Payload format
What Make 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 the HookDeploy app to Make.com? +
How fast do triggers fire? +
Is the webhook body decrypted before delivery? +
Can I filter which webhooks trigger a scenario? +
Ready to connect?
Create an endpoint, grab your API key, and add the Make.com integration from your dashboard.