How to set up webhooks on Make
Create a new scenario in Make.com, add a Custom Webhook module which auto-generates a unique HTTPS URL, copy that URL into your source app's webhook settings, test by triggering an event, map the incoming data, and activate the scenario. Most setups take 10-30 minutes.
Prerequisites
- Active Make.com account (free tier works for testing)
- Source app with webhook support (Stripe, GitHub, Discord, etc.)
- Admin access to configure webhooks in source app
- Basic understanding of JSON payloads
- Stable internet connection
Step-by-Step Instructions
Sign in and create a new scenario
Log in to your Make.com account and navigate to your dashboard. Click to create a new scenario or open an existing one where you want to add webhook functionality. This scenario will serve as the automation workflow triggered by incoming webhook data.
Add the Webhooks module
In the scenario editor, click the plus icon to add a new module. Search for Webhooks in the available apps and select it. This opens the webhook configuration options for your scenario.
Select Custom Webhook
From the webhook options, choose Custom Webhook. This module type generates a unique HTTPS URL that external services can send data to. Make.com also offers Custom Mailhook for email-based automation, but Custom Webhook provides greater flexibility for most integration needs.
Create and name your webhook
In the module configuration, click Add to create a new webhook. Enter a meaningful name (for example, PayFunnels or Stripe Events) so you can recognize it later. Click Save to confirm. Make.com automatically generates a unique webhook URL.
Copy the webhook URL
After creation, Make.com displays your unique webhook URL. Copy this entire URL to your clipboard. It will look something like https://hook.eu1.make.com/abc123xyz. You will paste this URL into your source application's webhook settings to establish the connection.
Configure the source app's webhook settings
Log in to your source application (Stripe, GitHub, Shopify, etc.) and navigate to its webhook or integration settings. Paste the Make.com webhook URL into the designated webhook endpoint field. Select which events should trigger the webhook (for example, 'payment.completed' in Stripe or 'push' events in GitHub). Save these settings in the source app.
Test the webhook connection
Return to Make.com and ensure your scenario is in edit mode. Trigger an event in your source application that should send data to the webhook (for example, submit a form, complete a payment, or push code). Watch the Make.com webhook module for incoming data. Click Re-determine data structure or Load samples to capture and display the payload structure.
Map webhook data to subsequent modules
Once data is received, Make.com parses the payload and displays available fields in the mapping panel. Add subsequent modules to your scenario (email, database, CRM, etc.) and map the webhook data fields to the inputs these modules require. For example, map the email field from the webhook to an email module's recipient field.
Configure optional API key authentication
For enhanced security, you can attach API keys to your webhook. In the webhook module configuration, click Add API Key and enter a name for the keychain. When making requests to your webhook, the source app must include this API key in the X-Make-ApiKey header. This prevents unauthorized access to your webhook endpoint.
Activate and monitor your scenario
After mapping all data and configuring subsequent modules, save your scenario. Toggle the scenario to ON using the switch in the top-right corner. Your webhook is now active and will trigger the workflow each time the source app sends data. Monitor the scenario's execution history to verify that data is flowing correctly and actions are executing as expected.
Common Issues & Troubleshooting
No data received or empty samples in webhook editor
Ensure your scenario is turned on (toggle in top-right). Verify you copied the exact Make webhook URL into the source app. Trigger an event in the source app to send data. Click 'Re-determine data structure' in Make to refresh and load samples.
Webhook URL not working or connection refused
Confirm the URL is copied exactly without extra spaces. Check that your Make.com account is active and the scenario exists. Verify your internet connection and that no firewall is blocking HTTPS requests. Test the URL by opening it in a browser; Make displays a default response page.
Payload format mismatch or missing fields in mapping
The source app may send data in a different format than expected. Click 'Re-determine data structure' in the webhook module and trigger a test event from the source app to capture the actual payload. Review the incoming data structure and adjust subsequent module mappings accordingly.
Webhook response timeout or 180-second limit exceeded
Make.com has a 180-second timeout for sending webhook responses. If your scenario takes longer, ensure you are not performing heavy processing in the webhook response module. Simplify the response or move complex logic to separate modules that execute after the response is sent.
API key authentication failing
If you configured API keys, verify that the source app is sending the key in the <code>X-Make-ApiKey</code> header with the exact name you specified. Check the source app's webhook request headers and ensure the key matches. Regenerate the API key in Make if needed.