Make.com Webhooks

Webhooks vs. Scheduled Triggers

Scheduled triggers check for new data at an interval — every 15 minutes, every hour. The maximum delay between an event and your automation responding is the interval length. For a 15-minute interval, a new lead can wait up to 15 minutes before the enrichment scenario runs.

Webhook triggers fire immediately when the source system sends data. When a form is submitted, the webhook is called immediately — your scenario starts within seconds.

Use webhooks whenever possible for:

• New lead notifications (should be immediate)
• Support ticket creation
• Payment received
• New signup
• Any event where speed matters

Use scheduled triggers for:

• Batch processing (e.g., daily report generation)
• Polling systems that don't support webhooks
• Aggregation workflows that process accumulated data

Setting Up a Webhook in Make.com

1. Create or open a scenario
2. Click the trigger module (+ button)
3. Search for "Webhooks" and select "Custom webhook"
4. Click "Add" to create a new webhook — Make.com generates a unique URL
5. Copy the webhook URL

Now configure the external service to POST to that URL when your event occurs. Each service is different — look for "Webhooks" or "Integrations" in the service's settings.

Getting the data structure: Click "Redetermine data structure" in the webhook module, then trigger a test event from the source service. Make.com receives the payload and maps all the fields — they become available for mapping in subsequent modules.

Common Webhook Sources

HubSpot: Settings → Integrations → Webhooks. Set up webhooks for contact created, deal stage changed, etc. HubSpot sends events to your Make.com webhook URL immediately.

Stripe: Dashboard → Developers → Webhooks. Select events (payment succeeded, subscription cancelled) and add your Make.com webhook URL.

Typeform: Form settings → Connect → Webhooks. Add your Make.com webhook URL. Fires when a form is submitted.

GitHub: Repository settings → Webhooks. Add your Make.com URL and select the events (push, pull request, etc.)

Custom applications: If you have a custom app, add code to POST to the Make.com webhook URL when relevant events occur — new user registered, order placed, etc.

Webhook Security

Webhook URLs are public by default — anyone who discovers the URL can POST to it and potentially trigger your automation. Secure your webhooks:

Secret token: Add a secret token to your webhook URL as a query parameter (?token=your-secret). In the scenario, add a filter right after the webhook: only continue if the token matches. Any request without the correct token stops immediately.

IP restriction: For Make.com Business plans, you can restrict webhook acceptance to specific IP ranges (e.g., only accept calls from HubSpot's IP ranges).

Header verification: Some services (Stripe, GitHub) include a cryptographic signature in the request headers. Verify this in a filter or Code module after the webhook.

Responding to Webhooks

By default, Make.com responds to webhooks immediately with "Accepted" (HTTP 202) — not waiting for the scenario to complete. The source service gets a fast response; the scenario processes asynchronously.

For scenarios where the sender needs a response (building an API endpoint):

1. Add a "Webhooks > Webhook response" module at the end of the scenario
2. Configure the HTTP status code and response body
3. Change the webhook trigger's "Response" setting to "Custom response"

The webhook will now wait for the scenario to complete before returning the response. This is useful when your scenario is acting as an API endpoint and the caller needs the result.

Debugging Webhooks

Webhook history: The webhook module shows a history of all received payloads. Click any past payload to see the exact data received — useful for debugging unexpected scenario behavior.

Make.com Webhook Inspector: The "Request Inspector" in the webhook trigger allows you to see incoming requests in real-time. Open it while triggering a test event to see exactly what was received.

Missed events: Webhooks don't queue missed events. If your scenario is off when a webhook fires, that event is missed. For critical workflows, build compensating logic (periodic catch-up scans) to recover from missed webhooks.

Recommended Tools

• Make.com — Webhook triggers and scenario execution
• HubSpot — Webhook integration for CRM events
• Stripe — Payment event webhooks
• Typeform — Form submission webhooks
• n8n — Alternative platform with similar webhook capabilities

“Webhooks transform Make.com from a scheduled batch processor into a real-time automation platform. For customer-facing workflows — lead follow-up, support tickets, payment processing — the difference in response time is meaningful.”