CF7 to Make (Integromat) Webhook Not Activating: A Complete Troubleshooting Guide

You have built a Contact Form 7 form. You have created a scenario in Make. You have pasted the webhook URL into your WordPress dashboard. And yet, when a user submits the form, nothing happens in Make. The scenario never activates.

This is a frustratingly common problem. The good news? The issue is almost always one of four things, and each has a clear fix. This guide walks through the exact debugging process, common error patterns, and verified solutions.

Understanding the Data Flow

When a user submits your CF7 form with a Make webhook enabled, here is what should happen:

User submits form → CF7 processes submission → Webhook URL called → Make captures data → Scenario runs

When it breaks, the failure happens at one of the last three stages. Your first diagnostic tool is the Make scenario history. It shows whether a webhook request was received at all, and if so, what data was captured.

If no request appears in Make, the problem is on the WordPress side. For a deeper breakdown of data not reaching your endpoint, see this guide on Contact Form 7 data not reaching the API.

Failure #1: The Webhook URL Was Not Saved in the Database

What you see: Make shows no incoming data. The webhook URL appears to save in the WordPress admin, but after refreshing the page, the field is blank again.

Why it happens: This is a known bug with the CF7 Redirections, Integrations, and Database plugin. The webhook URL is actually being saved to the database, but it is not appearing in the admin interface. This gives the false impression that the save failed.

The fix:

Step 1: Access your WordPress database using phpMyAdmin or a similar tool.

Step 2: Navigate to the wp_postmeta table. Search for the meta key _cf7rid_integromat.

Step 3: Check the meta_value column for that key. If the webhook URL is present, the data was saved correctly.

Step 4: Even if the admin shows a blank field, the webhook should still fire. Submit a test form and check Make for incoming data.

How to verify: If the webhook fires successfully despite the admin showing a blank field, the issue is purely cosmetic. The integration is working.

Failure #2: The CF7 Integration Plugin Is Not Compatible

What you see: No webhook request is sent at all. Make remains empty.

Why it happens: Make's official documentation acknowledges "ongoing issues" with certain CF7 integration plugins. The recommended solution is to use a different plugin that is known to work reliably with Make.

The fix:

Step 1: Check which plugin you are using. Make's documentation specifically recommends the CF7 to Webhook plugin as a reliable alternative.

Step 2: Switch plugins if necessary. Deactivate your current integration plugin and install CF7 to Webhook. Reconfigure the webhook URL in the new plugin's settings.

Step 3: Verify the webhook fires. Submit a test form and confirm that Make receives the data.

Pro tip: The Redirection for Contact Form 7 plugin (from Themeisle) also supports Make integration reliably, but it requires the Marketer plan or higher.

Failure #3: The Scenario Is Not Active or Listening

What you see: The webhook URL is configured correctly, but Make does not capture the first submission.

Why it happens: Make scenarios must be running or listening to receive webhook data. If the scenario is turned off, or if you have not clicked "Run once" to put it in listening mode, the webhook will not be processed.

The fix:

Step 1: Open your Make scenario. Click the "Run once" button to put the scenario in listening mode.

Step 2: While Make is listening, submit your CF7 form with test data.

Step 3: Return to Make. You should see the captured data appear in the webhook module. Click the bubble to inspect the data.

Step 4: Once you have confirmed the data structure, save the scenario and toggle it ON using the switch in the bottom left corner.

Common mistake: Submitting the form before the scenario is active. A WordPress user reported that they had to activate the Make scenario before submitting the form, otherwise it returned an error because the webhook was not ready.

Failure #4: The Request Method or Payload Format Is Wrong

What you see: Make receives a request, but the data is empty or malformed. Or Make returns an error.

Why it happens: Make's webhook endpoint expects data in a specific format. If the request method is not POST, or if the Content-Type header is missing, Make may reject or ignore the payload.

The fix:

Step 1: Verify the request method. In your plugin integration settings, ensure the HTTP method is set to POST.

Step 2: Set the Content-Type header. In the Request Headers section, add:

Content-Type: application/json

Step 3: Check the payload structure. Ensure your field mapping produces valid JSON. A common mistake is sending flat key-value pairs without proper JSON formatting. Your payload should look like:

{
  "name": "[your-name]",
  "email": "[your-email]",
  "message": "[your-message]"
}

For a deeper dive into JSON structure mapping, read this guide on Contact Form 7 JSON mapping.

The Debugging Checklist

Work through this sequence every time a webhook fails to activate:

Step	Action	What It Tells You
1	Check Make scenario history	Was a request received? If not, the problem is in WordPress.
2	Check the database for _cf7rid_integromat	Confirms whether the webhook URL was actually saved.
3	Click "Run once" in Make	Puts the scenario in listening mode for test data.
4	Submit a test form while Make is listening	Confirms the connection end-to-end.
5	Verify request method is POST	Make expects POST, not GET.
6	Check Content-Type header	Missing application/json can cause parsing failures.
7	Check CF7 email settings	Rules out earlier-stage submission failures.

For a comprehensive breakdown of authentication and error handling across different APIs, see this guide on Contact Form 7 API authentication errors.

Beyond Make: One Form, Multiple Destinations

Once your Make webhook works, you might want to send the same form submission to other tools: a CRM, an email marketing platform, or a help desk system.

A good connector plugin supports multiple API integrations and webhooks from a single form submission. You can trigger a Make scenario, create a CRM contact, send an SMS via Twilio, and create a Zendesk ticket, all from one CF7 submission. For a cost comparison, see this article on Zapier vs a dedicated API plugin.

Key Takeaways

The webhook URL may save to the database even if the admin shows it as blank. Check the wp_postmeta table for _cf7rid_integromat to verify.

Make's documentation recommends the CF7 to Webhook plugin. Some CF7 integration plugins have known compatibility issues with Make.

The scenario must be listening before you submit a test form. Click "Run once" in Make, then submit your form.

Make expects POST with JSON. Set the method to POST and add the Content-Type: application/json header.

Make's scenario history is your first diagnostic tool. If no request appears there, the problem is on the WordPress side.

With the correct URL, a compatible plugin, and a scenario that is actively listening, your CF7-to-Make integration will fire reliably on every form submission.