Skip to content

How to Connect to Zapier Webhook from a WordPress Form?

Key Takeaways

  • Form block in Nexter Blocks Pro sends every submission to a webhook URL as a JSON POST request, so Zapier can receive the form data.
  • Zapier setup uses the Webhooks by Zapier trigger with the Catch Hook event, and the copied URL goes into the Form block’s WebHook panel.
  • Unique ID settings keep field names stable, because without them Zapier receives labels with spaces replaced by underscores, and changing a label later can break the Zap.
Table of Contents

A webhook sends your form data to Zapier, so each submission can add a CRM contact, a spreadsheet row or anything else.

The Form block in Nexter Blocks Pro posts every submission to a webhook URL.

For every Form setting in one place, see the Form block guide.

Before You Start

  • Edition: Pro — The Webhook action needs Nexter Blocks Pro.
  • Block to enable: Form, switched on under Nexter > Blocks in your WordPress dashboard.
  • A webhook URL: in Zapier, create a Zap with the Webhooks by Zapier trigger and Catch Hook event, then copy its URL. See Zapier’s webhook guide.

Learn via Video Tutorial

Steps

  1. Add the Form block to your page, click Design from Scratch and choose Simple Contact Form or Newsletter Form.
  1. Select the Form block (not a field inside it). In Action After Submit, open Options and choose Webhook. You can keep Email selected as well.
The Action After Submit panel with Options
  1. Open the WebHook panel that appears and paste your webhook URL into URL.
The WebHook panel with the URL field
  1. Optional: select each field and enter a short key, such as email, in its Unique ID setting. These become the field names Zapier receives.
A Name Field with the Unique ID setting
  1. Save the page, then submit the form once on the front end to test the connection.

How It Behaves

  • Each submission is sent as a JSON POST request to the URL.
  • Fields with a Unique ID are sent under that key. Without Unique IDs, each field is sent under its label, with spaces replaced by underscores (for example Full_Name).
  • In Zapier, click Test trigger after a test submission to see the fields.

Limitations

  • Pro only.
  • The URL must be publicly reachable. Local or private network addresses are rejected.
  • Changing a field label later changes its key unless you set a Unique ID, which can break your Zap.

Troubleshooting

Zapier shows different field names than before

A label was edited. Set a Unique ID on every field so the keys stay the same.

The visitor sees “A valid URL was not provided”

Paste the full https:// webhook URL into the URL field.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Related Frequently Asked Questions

What do I need before connecting a WordPress form to Zapier Webhooks?

Nexter Blocks Pro is required, because the Webhook action only works in the Pro edition. The Form block also has to be enabled under Nexter > Blocks in your WordPress dashboard. On the Zapier side, you need a Zap with the Webhooks by Zapier trigger and the Catch Hook event, then copy that webhook URL. That setup matters because the form posts every submission directly to that URL.

How do I send WordPress form submissions to a Zapier webhook?

The form sends each submission as a JSON POST request to the webhook URL, so Zapier receives structured data instead of plain text. In Nexter Blocks, the key detail is using Action After Submit set to Webhook and pasting the full URL into the WebHook panel. If you want stable field names in Zapier, give each field a Unique ID first.

Why do Zapier field names change when I edit a form label?

Field names can change because labels become the key when no Unique ID is set. The page says editing a label later changes its key unless you set a Unique ID, which can break your Zap. The safer approach is to assign a short Unique ID like email to every field so Zapier keeps receiving the same names even if labels change later.

What should I do if Zapier shows different field names than before?

That usually means a label was edited after the first test submission. Nexter Blocks sends fields under their label when no Unique ID exists, so changing the label changes the key. Setting a Unique ID on every field fixes that by locking the field name in place, which is important if your Zap depends on exact keys.

Why does WordPress show 'A valid URL was not provided' for my webhook?

That error points to an incomplete webhook value in the URL field. The page says to paste the full https:// webhook URL into URL, not a partial link or missing protocol. This matters because Nexter Blocks Pro posts submissions directly to that address, and Zapier needs the exact public endpoint to accept the request.

Can I use a local or private network URL for this Zapier connection?

No, because the webhook URL must be publicly reachable. The page explicitly says local or private network addresses are rejected. That limitation matters for testing setups on localhost or internal networks, since Zapier cannot receive submissions from an address it cannot reach from the public internet.

Last reviewed: September 14, 2026

Related Docs