Start with the signup
Use a popup, inline form or multistep campaign to collect the contact details and answers your workflow needs.
Explore forms & popupsSend 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.
Join the waitlist for our next design workshop.
Choose Zapier, Make or n8n in WConvert’s webhook setup. Connect your receiver, then decide what happens after each signup in your automation tool.
Turn a new signup into the first step of your Zap. Add your next actions in Zapier.
Connect ZapierBring signups into a Make scenario, then route the details to the apps you use.
Connect MakeReceive signups in an n8n Webhook node and build the follow-up around your team.
Connect n8nSend signups to your own endpoint. Verify the signature and handle the next action in your code.
Build your receiverAll four options use webhooks included in WConvert Pro. Service plans and workflow charges are separate.
Use a popup, inline form or multistep campaign to collect the contact details and answers your workflow needs.
Explore forms & popupsUse 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 guideThe webhook adds a delivery step to your captured lead. You can still review and export submissions from WConvert.
Explore lead managementYou 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.
In Settings → Connections & destinations, choose Connect an account, then Webhook. Choose your tool and enter its receiver URL and any required authentication headers.
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.
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 guideIllustrated 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.
Pass contact details and enquiry answers to a workflow that creates or updates a record in your CRM.
Configure your receiver to add waitlist submissions to a spreadsheet your team can review.
Use a received callback request to trigger a team notification in your chosen automation tool.
Your campaign fields and format may depend on your WConvert edition; follow-up actions are configured separately in your receiving tool.
Your receiver decides what happens next. Account for new submissions, temporary failures and people who complete more than one signup step.
Alex submits an email and a preferred session.
A signed JSON request carries the contact, campaign and answers.
A successful receiver response marks the request delivered. The CRM update, spreadsheet row or notification depends on the actions you configure in that receiver.
A timeout or temporary server error interrupts delivery.
Retries keep the same event ID so your receiver can recognize duplicates.
Temporary failures are retried on WordPress’s scheduler. Your receiver must ignore an event ID it has already processed. After the last retry, review the send status and resend once the receiver works.
Alex completes two separate signup steps in one campaign.
The second request includes both the email and phone number.
The requests have different event IDs and the same lead ID. Match by lead ID or email in your workflow so the second step updates the existing record.
Illustrates connection behavior. No data is submitted or sent.
The details that matter when choosing Webhooks for your workflow.
Full webhook setup guideYes. Webhooks are included in Pro. Your automation platform may charge separately for webhook access, tasks or workflow runs.
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.
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.
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.
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.
No. Deleting a lead in WConvert does not delete copies at the receiver or in downstream tools. Manage those copies separately.
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.