Make.com

HookDeploy’s Make.com integration lets you trigger scenarios the instant a webhook is captured — or when a delivery succeeds or fails. The integration uses Make’s Dedicated URL pattern for instant delivery, not polling.

Prerequisites

• A HookDeploy account (sign up free)
• A Make.com account (Free plan or above)

Connecting your account

1. In your HookDeploy dashboard, go to Integrations and click the Make.com invite link. This adds the HookDeploy app to your Make account.
2. In Make.com, create a new scenario and add a HookDeploy module.
3. Click Add next to the Connection field.
4. Enter your HookDeploy API key (hd_live_xxxx). Find this in your dashboard under Settings → API Keys.
5. Click Save. Make validates the key immediately against your org.

Your connection label will show your organization name and current plan.

Triggers

Triggers fire automatically when the corresponding event occurs in HookDeploy. All three triggers deliver the same webhook envelope.

New Webhook Received

Fires within 1–2 seconds when a webhook is captured on your endpoint.

Configuration

Output — see Payload envelope.

Forwarding Succeeded

Fires when HookDeploy successfully delivers a webhook to a forward destination (HTTP 2xx response received).

Configuration

Output

Forwarding Failed

Fires when a delivery attempt returns a non-2xx status or times out.

Configuration — same as Forwarding Succeeded.

Output — same fields as Forwarding Succeeded, plus:

Actions

Create Endpoint

Creates a new webhook endpoint in your org.

Input

Output — Returns the created endpoint object including id, slug, url, and created_at.

Pause Endpoint

Pauses webhook capture on an endpoint. Incoming webhooks receive 423 Locked and are not captured or forwarded.

Input

Resume Endpoint

Resumes a paused endpoint.

Input — same as Pause Endpoint.

Replay Request

Re-delivers a previously captured webhook to a target URL.

Input

Output

Invite Member

Invites a new member to your organization. Sends the invitation email automatically.

Requires an API key created by an Admin or Super Admin.

Input

Deactivate Member

Immediately revokes a member’s access. Data and history are preserved; the member can be reactivated without a new invitation.

Requires an Admin or Super Admin API key.

Input

Reactivate Member

Restores access for a previously deactivated member. Access is restored immediately with the member’s original role.

Input — same as Deactivate Member.

Searches

Get Request

Retrieves a single captured webhook request with its full decrypted payload.

Input

Output — Returns the full request object including method, headers, body, query, source_ip, body_size_bytes, and created_at.

List Requests

Returns recent captured requests for an endpoint.

Input

Output — Array of request objects (same fields as Get Request, body omitted for performance).

List Endpoints

Returns all endpoints in your org. Primarily used to power dynamic dropdowns in other modules, but available as a search module for lookup scenarios.

Input

Output — Array of endpoint objects including id, name, slug, url, paused, and created_at.

Payload envelope

All three trigger modules deliver the same structured output:

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

All fields in headers, body, and query are available for mapping in any Make.com module. HookDeploy decrypts the payload server-side before delivery — Make.com always receives plaintext.

Common scenarios

Stripe payment → Google Sheets row

1. Trigger: New Webhook Received on your Stripe endpoint
2. Filter: body.type equals payment_intent.succeeded
3. Action: Google Sheets — Add a Row
   • Map body.data.object.amount → Amount column
   • Map body.data.object.currency → Currency column
   • Map hookdeploy.captured_at → Timestamp column

Delivery failure → Slack alert + auto-retry

1. Trigger: Forwarding Failed on your endpoint
2. Action: Slack — Create a Message with destination.name and result.error_message
3. Module: Sleep (5 minutes)
4. Action: HookDeploy — Replay Request using hookdeploy.request_id

GitHub push → Jira ticket

1. Trigger: New Webhook Received on your GitHub endpoint
2. Filter: headers.x-github-event equals push
3. Action: Jira — Create an Issue
   • Summary: map from body.head_commit.message
   • Description: map from body.repository.full_name

Troubleshooting

Trigger not firing Confirm the endpoint is not paused in your HookDeploy dashboard. Paused endpoints return 423 Locked; they do not capture, forward, or trigger subscriptions.

Empty body, headers, or query fields This can occur if the scenario was tested using Make’s “Run once” button before a real webhook arrived. Send a real webhook to your endpoint to populate sample data, then re-run the scenario.

403 forbidden on member actions Member management endpoints require an API key created by an Admin or Super Admin. Developer, viewer, and finance keys return 403 on these routes. Create a new API key with the correct permissions.

Subscription auto-disabled HookDeploy automatically disables a Make.com subscription after 10 consecutive delivery failures. If your scenario errors repeatedly, the connection to your Make webhook URL may be broken. Re-enable it by editing the trigger module and re-saving the connection.

Plan limits

All plans including Free include Make.com integration. Payload size and retention limits apply per plan: