Your leads are always saved in WordPress first. If a delivery fails, the lead is kept and retried automatically, so nothing is lost.
Webhook test fails
- Check the Webhook URL is the full address your tool gave you, with no spaces.
- Check Send leads to this webhook is ticked and you clicked Save Changes.
- In Zapier, Make or n8n, make sure the webhook is listening (for example, in n8n use the production URL with the workflow active).
- If you set a Signing secret, make sure the receiving end uses the same secret to check the X-WPLP-Signature header, or leave it blank.
- Click Send a test lead to this webhook again and check Recent deliveries.
Still failing?
The webhook is the recommended route for any email tool. If FluentCRM or Mailchimp won’t connect, send leads through the webhook instead (see Sending leads to a webhook).
FluentCRM test fails
- If you see FluentCRM is not active on this site yet, install and activate FluentCRM.
- Check Lists and Tags contain IDs (numbers) separated by commas, not names.
Mailchimp test fails
- Check the API key is complete, including the ending such as -us21.
- Check the Audience ID comes from Audience settings in Mailchimp.
Reading Recent deliveries
Each attempt is listed with the connection name, the time and the outcome. If the receiving end replied, you’ll see its status code, for example 404 (wrong address) or 500 (a problem at their end). If the request couldn’t be made at all, you’ll see the error text, such as a timeout or a DNS failure. A queued delivery also shows how many attempts have been made. Failed deliveries are retried automatically up to six times, and the lead stays safe in WordPress throughout.
Still stuck? Open a ticket on the support page on ABC and a real person will help.
Was this article helpful?