Most operators who use Make for automation rely on scheduled triggers — run this workflow every hour, every day. Webhooks flip the model: instead of Make asking “is there anything to do?”, your landing page tells Make “something just happened.”

The difference matters for responsiveness. A scheduled workflow might lag by up to an hour. A webhook-triggered workflow runs within seconds of the triggering event.

Quick Answer: A webhook is a URL that Make gives you. When your landing page (or any other system) sends a POST request to that URL, Make receives the data and runs the workflow immediately. Setup in Make takes under 10 minutes. The key steps: create a webhook trigger in Make, connect your form or landing page to send POST requests to that URL, and build the workflow that processes the incoming data.

What a webhook actually is

A webhook is an HTTP endpoint — a URL — that your Make workflow listens on. When something sends data to that URL (via a POST request), Make receives it and the workflow runs.

Contrast this with polling: Make checks an email inbox or spreadsheet every X minutes to see if new data has arrived. Webhooks reverse the direction — your landing page notifies Make the moment something happens.

For affiliate operators, webhooks are useful for:

  • Processing lead form submissions from landing pages
  • Triggering follow-up workflows when someone clicks an affiliate link and converts
  • Receiving notifications from third-party tools (payment processors, email platforms) when events happen
  • Connecting custom-built pages to your automation stack without a native integration

Setting up a webhook in Make

Step 1 — Create a webhook trigger

In Make, create a new scenario. For the trigger, search for “Webhooks” and select “Custom webhook.” Make will give you a unique URL that looks like: https://hook.eu1.make.com/abc123xyz

Copy this URL. This is the endpoint your landing page will send data to.

Step 2 — Define the data structure

Make needs to know what data to expect. The easiest way: click “Redetermine data structure” in the webhook module, then trigger a test submission from your form. Make captures the incoming data and learns the field names.

After the test, your webhook module will show the fields your form sends — name, email, phone, source, etc. — and you can reference these in downstream modules.

Step 3 — Build the workflow

After the webhook trigger, add the modules that process the incoming data:

  • Google Sheets: Add a row to a leads spreadsheet
  • Gmail / Mailchimp: Send a welcome email or add to a list
  • Slack: Post a notification to a channel
  • HTTP module: Forward the data to another API
  • Filter: Only process submissions that meet certain criteria (e.g., submissions with a valid email)

Save and activate the scenario.

Connecting your landing page

Your landing page needs to send a POST request to the Make webhook URL when the form submits.

Option A — Form builder with webhook support

Most form builders (Typeform, Tally, JotForm) have native webhook support. In the form settings, find “Integrations” or “Webhooks” and paste the Make URL. Test with a submission — Make should receive the data.

Option B — Custom HTML form

For a custom HTML landing page, add a small JavaScript snippet that intercepts the form submission and sends it to the Make webhook:

document.getElementById('lead-form').addEventListener('submit', async function(e) {
  e.preventDefault();
  const formData = Object.fromEntries(new FormData(this));
  await fetch('https://hook.eu1.make.com/YOUR_WEBHOOK_ID', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify(formData)
  });
  // Show success message to user
  document.getElementById('success-msg').style.display = 'block';
});

Replace YOUR_WEBHOOK_ID with the ID from your Make webhook URL. The form data is sent as JSON when the user submits.

Option C — No-code page builders

Webflow, Framer, and similar builders have webhook integrations. In most cases, add the Make webhook URL in the form settings under “Integrations” or “Form submissions.”

Practical patterns for affiliate operators

Lead capture → email sequence

Landing page collects email → webhook triggers Make → Make adds lead to Mailchimp or Beehiiv list → automated email sequence starts.

This replaces manual CSV exports and list imports. Every submission is processed immediately and enters the sequence within seconds.

Conversion event tracking

When a referred visitor converts on a partner’s landing page (assuming the partner can send webhook notifications on conversion), the webhook triggers your attribution workflow — logging the conversion, updating your tracking spreadsheet, sending you a Telegram notification.

Most affiliate platforms don’t send webhooks on referral conversion. But if you’re running your own checkout or using tools that support conversion webhooks (Stripe, Gumroad), this is achievable.

Content request intake

A landing page where readers request a specific review or tutorial → webhook triggers Make → Make logs the request to a Notion database or Google Sheet → you review weekly and add popular requests to the content calendar.

This creates a lightweight reader-to-content-pipeline that doesn’t require you to monitor an inbox.

Debugging webhook issues

Make shows no data received: Confirm the POST request is being sent to the correct URL. Use Make’s “Run once” mode to watch for incoming requests in real time.

Data received but fields are empty: The form may be sending data in a format Make doesn’t expect (multipart form data vs. JSON). Check the incoming payload in Make’s scenario history and adjust the form’s content type.

Workflow runs but actions fail: Usually a mapping issue — a downstream module is referencing a field that isn’t present in the webhook data. Check the data structure in the webhook module and re-map fields.

Webhook URL stops working: Make webhook URLs don’t expire, but inactive scenarios can be deactivated. Ensure the scenario is active. If you deleted and recreated the webhook, update the URL in your form.

For the broader comparison of Make vs. n8n for publishing pipelines, see n8n vs Make for AI publishing. The Make affiliate program has commission details if you’re evaluating Make for affiliate promotion.

Frequently Asked Questions

Is there a limit on how many webhook calls Make can receive? Make’s free plan has limited operations. Each webhook call consumes operations for each module in the scenario. On paid plans, limits are higher. Check your plan’s operation count before building high-volume webhook workflows.

Can I use the same webhook URL for multiple forms? Yes — one Make webhook URL can receive data from multiple sources. Add a filter or router module in Make to handle different sources differently based on an identifier field in the form data.

How do I secure my webhook URL? Make webhook URLs are long random strings — effectively a secret. Don’t publish them publicly. For additional security, Make supports webhook header verification (you can require a specific header value from the sending system).

Can webhooks handle file uploads? Make webhooks can receive file data, but handling files (attachments, images) requires additional modules and depends on how the form sends the file. Text-based form data is simpler. For file upload workflows, evaluate dedicated file handling integrations.

Do I need a paid Make plan for webhooks? Make’s free plan includes webhooks. The limit is on total operations per month, not on webhook access specifically.

Automate your affiliate workflow

If you’re building automation workflows for your affiliate operation — lead capture, content scheduling, performance tracking — the Make affiliate program page covers what Make’s affiliate program looks like, and the programs section covers other automation platforms worth comparing.