WConvert+Webhooks
Included in WConvert Pro

Your next signup.
Your own workflow.

Send signups from your WordPress forms and popups to Zapier, Make, n8n or your own code. Capture the lead with WConvert, then put it to work in the tools your team uses.

FIELDWORK / STUDIO SESSIONS

A fresh perspective. A place on the list.

Join the waitlist for our next design workshop.

Join the waitlist
Email me about this workshop. Joining the waitlist does not reserve a place.
YOUR CONFIGURED CONNECTION
YOUR WEBHOOK RECEIVERWorkshop waitlist workflow
Configure the next actions in your receiver.
WConvert edition
Pro
Connect to
Zapier, Make, n8n or your code
What is sent
Signed JSON per submission
Temporary failures
Automatic retries
CHOOSE WHERE SIGNUPS GO

Tools you know.
Workflows you choose.

Choose Zapier, Make or n8n in WConvert’s webhook setup. Connect your receiver, then decide what happens after each signup in your automation tool.

All four options use webhooks included in WConvert Pro. Service plans and workflow charges are separate.

YOUR FORMS. YOUR EXISTING WORKFLOW.

A better way to join.
A familiar place to follow up.

Start with the signup

Use a popup, inline form or multistep campaign to collect the contact details and answers your workflow needs.

Explore forms & popups

Connect your next action

Use the received signup to add a CRM record, update a spreadsheet or notify your team. Set up those actions in Zapier, Make, n8n or your own code.

Read the webhook setup guide

Keep the lead in WordPress

The webhook adds a delivery step to your captured lead. You can still review and export submissions from WConvert.

Explore lead management
CONNECT ONCE. REUSE IN YOUR CAMPAIGNS.

Choose what matters.
Connect your workflow.

You need WConvert Pro and a publicly reachable receiver URL. Prepare a Zapier Catch Hook, a Make custom webhook, an n8n Webhook node or your own endpoint.

  1. Connect your receiver

    In Settings → Connections & destinations, choose Connect an account, then Webhook. Choose your tool and enter its receiver URL and any required authentication headers.

  2. Choose the campaign

    Save the account, add a Webhook destination and enable it in your campaign’s Destinations tab. Your own code should verify the request signature using the signing secret.

  3. Test the whole workflow

    Use Send a test from the campaign to send sample answers to your receiver. Configure the next actions there, then publish and check a real submission from start to finish.

Destinations are reusable. Changing a shared destination affects the campaigns using it.

Follow the full setup guide
Accepted submission → signed JSON

One signup. Useful context.

Your campaign’s configured handoff
Event
lead.captured
Contact
Alex Jordan · [email protected]
Campaign
Workshop waitlist
Answer
Preferred session: Design systems
Also included
Source, consent and submission identifiers
WebhooksDestination
YOUR WEBHOOK RECEIVERWorkshop waitlist workflow

Illustrated subset of a fixed payload. Webhooks send the submission snapshot; there is no field picker or custom body template. Map the received data in your workflow tool.

GIVE THEM A REASON TO CONNECT

The right invitation.
For your next campaign.

Your campaign fields and format may depend on your WConvert edition; follow-up actions are configured separately in your receiving tool.

WHAT HAPPENS AFTER THE SIGNUP?

A new connection.
The details matter.

Your receiver decides what happens next. Account for new submissions, temporary failures and people who complete more than one signup step.

AJ
Alex Jordan[email protected] · Example contact
BEFORE THE HANDOFF

A visitor joins the waitlist

Alex submits an email and a preferred session.

AFTER THE HANDOFF

Your receiver gets the signup

A signed JSON request carries the contact, campaign and answers.

Delivery is the first step

A successful receiver response marks the request delivered. The CRM update, spreadsheet row or notification depends on the actions you configure in that receiver.

Illustrates connection behavior. No data is submitted or sent.

GOOD TO KNOW

Before you
connect.

The details that matter when choosing Webhooks for your workflow.

Full webhook setup guide
Do I need WConvert Pro?

Yes. Webhooks are included in Pro. Your automation platform may charge separately for webhook access, tasks or workflow runs.

Can I use Zapier now?

Yes. Use Webhooks by Zapier with a Catch Hook and connect its URL in WConvert. Choose Zapier in WConvert’s webhook setup; this connection uses Webhooks by Zapier with WConvert Pro. Make and n8n also accept webhook submissions.

Can I choose which fields are sent?

The webhook uses one fixed JSON payload containing contact details, answers, campaign, source and consent information. There is no field picker or custom body template. Select and map what you need in the receiving workflow. IP addresses and browser details are not sent.

Are webhook requests signed?

Yes. Each request includes a Standard Webhooks signature. Your own code should verify it with the signing secret. Zapier, Make and n8n do not check that signature automatically; use the receiver URL and any supported authentication headers as described in the setup guide.

What if delivery fails?

WConvert retries temporary failures such as timeouts, rate limits and server errors. Other problems, such as rejected credentials or a redirect, need attention. Retries rely on WordPress’s scheduler and can be delayed on low-traffic sites. The guide explains send statuses, retry timing and duplicate handling.

Does deleting a lead remove it from my other tools?

No. Deleting a lead in WConvert does not delete copies at the receiver or in downstream tools. Manage those copies separately.

WCONVERT + WEBHOOKS

A better invitation.
A familiar place to follow up.

Choose your form, connect your service and give visitors a reason to come back.

Find your WConvert plan Explore all connections WConvert Free is available on WordPress.org. Pro checkout is available now. Provider charges may apply separately.