Webhook Support

Webhook Support#

In addition to the built-in CRM and ESP integrations, WP Smart Consent can fire an outbound webhook on every opt-in event. This lets you connect to any service that accepts an incoming HTTP POST request — useful for platforms not covered by the built-in integrations, or for routing opt-ins through an automation tool like Zapier, Make, or n8n.

How It Works#

When a visitor opts in, WP Smart Consent sends a POST request to the URL you’ve configured, with the contact’s data in the JSON body. This fires alongside any other enabled integrations — the webhook is just another destination, not a replacement for them.

Setting It Up#

In the WP Smart Consent dashboard, go to Integrations and find the Webhook card. Enable it, paste in your target URL, and save. That’s all that’s required for basic use.

The Data Payload#

The JSON body sent with each webhook request includes the contact’s name and email address. If you need to limit what’s included — for example, if the receiving service only expects an email field — the optional data filter lets you restrict the payload to specific fields only.

Using a Webhook With Automation Platforms#

If you’re routing through an automation platform like Zapier or Make, point the webhook URL at your automation’s incoming webhook trigger. From there you can map the fields and forward the contact to any service your automation platform supports — giving you access to hundreds of additional destinations beyond WP Smart Consent’s built-in list.

One Webhook URL#

The current version supports a single webhook destination. If you need to send opt-ins to multiple external endpoints, an automation platform in the middle is the practical solution — receive the single webhook and fan it out to as many services as needed.