There are some situations in which WP Fusion doesn’t receive webhooks properly.
The best method to test this is to enable logging by going to Settings >> WP Fusion >> Advanced, and checking the box “Enable Logging”. Then try and send a webhook from your CRM and see if anything is recorded in the logs.
If nothing is showing up in the logs, you can test the webhook manually by visiting the webhook URL in your browser. This will be the same URL you used when setting up the webhook in your CRM, and you can select a contact ID to use for testing. For example
Replace ACCESSKEY with your access key from the settings, and CID with a contact ID you’d like to use to test. You should see a success message showing that the user was updated. If there were any errors, they’ll be reported there as well.
Making sure the automation is working correctly
If you’re sending the webhook as part of a complex automation in your CRM, it might help to make sure the webhook is actually being sent in the first place. You can use a third party service for this, like https://webhook.site/. This will give you a unique URL, like https://webhook.site/#/bd662d92-fb16-4431-ae79-f566943b0f9e, which you can paste into the URL field for the webhook in your CRM.
Send a contact through the automation or rule, and you should see a message appear on webhook.site showing the incoming data. If this works then you know the webhooks are being sent correctly.
Security software running on your site or server can also block incoming webhooks. If the URL works when visited manually in your browser, but not when being sent by your CRM, try disabling any security plugins and sending the webhook again.
If that doesn’t work, it’s also possible that your hosting company is blocking the webhooks for security reasons. You can contact your host, or look at your host’s security logs, to see if any traffic is being blocked. If so, they should be able to create an exception for you by modifying their security rules.
The Async Method
If you’re sending many webhooks simultaneously (100+) it’s possible your web server is unable to process them in time and runs out of available resources. To prevent this, you can try WP Fusion’s (experimental) asynchronous method for processing webhooks.
To enable this, append &async=true to the end of your webhook URL. For example:
This will tell WP Fusion to put the incoming webhooks in a queue, and work through them over a period of time, taking into account your server’s available resources.
This feature is still experimental while we receive feedback, so if you encounter any unexpected behavior please let us know.