¶ Troubleshooting Guide for Custom Webhook Actions in Workflows
This guide is designed to help you troubleshoot common issues related to Custom Webhook Actions within workflows. These actions enable real-time data exchange with external systems using customizable request formats. If your webhooks are not triggering, failing to send, or returning unexpected responses, this FAQ provides quick solutions to help you identify and resolve the issue. Each answer includes concise steps, making it easy to incorporate visuals or examples where needed.
¶ FAQ’s
Question: Why is my webhook action marked as “Failed” in the workflow history?
Answer:**
**This usually happens when the external API returns an error or cannot be reached.
How to Fix:
Double-check the URL used in the webhook for typos or invalid endpoints.
- Ensure the server you’re sending to is online and can handle incoming requests.
Steps:
- Copy the webhook URL and test it using a third-party tool (like Postman).
- Check the workflow execution history to see the error message returned.
Make sure the server supports the HTTP method (POST, GET, etc.) you selected.
Question: My webhook is not sending the correct data. What’s wrong?
Answer:**
**Incorrect data mapping or missing custom values can cause this issue.
How to Fix:
- Review the request body and make sure all fields are correctly mapped.
- Use the autocomplete suggestions to pull in the right values from contact records or incoming webhook variables.
Steps:
- Go to the webhook step in your workflow.
- Expand the body section and recheck each field’s value.
Use the {} icon or autocomplete field list to insert accurate variables.
Question: The receiving server is throttling or rejecting some requests. How do I prevent this?
Answer:**
**This happens when you’re sending too many requests too quickly, exceeding the server’s rate limit.
How to Fix:
- Slow down the workflow by using a wait step before the webhook.
- Add contacts in batches to avoid overwhelming the server.
Steps:
- Insert a Wait Step before the webhook (e.g., 1 min delay).
- Space out contact entries into the workflow (avoid bulk adding large lists).
- Coordinate with the receiving system to understand rate limits.
Question: My webhook is working, but the external system isn’t doing anything with the data.
Answer:**
**The data may not be in the correct format or structure the receiving system expects.
How to Fix:
- Check the API documentation of the system you’re sending data to.
- Make sure headers (like Content-Type: application/json) and request bodies match their format.
Steps:
1. Under webhook settings, verify that the correct headers are used.
2. Ensure you’re sending data in the required structure (JSON, query parameters, etc.).
3. Test your webhook with a known working sample request to isolate the issue.
Question: I’m not seeing any errors, but the webhook action seems to be skipped.
Answer:**
**Silent skips can happen if the workflow retries and still fails due to silent rejections from the external API.
How to Fix:
- Check if the webhook is configured with authentication and the token/key has expired or is invalid.
- Review the retry attempts and response codes in the contact’s workflow history.
Steps:
1. Confirm your authorization method is correct (e.g., Bearer Token, Basic Auth).
2. Regenerate or re-enter your credentials.
3. Re-add the contact to the workflow after fixing the issue.
Question: Can I test the webhook setup before sending live data?
Answer:**
While there isn’t a preview mode, you can create atest contact** and send test data through the webhook step.
How to Test:
- Use a dummy contact with known values.
- Observe the workflow history to ensure the webhook executes successfully and returns the correct response.
Steps:
- Create a test contact.
- Add that contact to the workflow manually.
- Monitor the webhook step’s execution log under workflow history.
Question: Why aren’t my query parameters or headers being recognized by the external system?
Answer:**
**Incorrect formatting or missing key-value pairs can cause this issue.
How to Fix:
- Review the Query Parameters and Headers section in your webhook setup.
- Make sure each field is filled properly and follows the external system’s expected keys.
Steps:
- In the webhook settings, expand Headers and Query Parameters.
- Confirm all fields are correctly filled (no extra spaces or missing keys).
- Save the workflow and retest using a test contact.
Question: The webhook worked once, but now it’s failing for new contacts. What changed?
Answer:**
**A likely cause is updated custom values or deleted fields used in the webhook mapping.
How to Fix:
- Review any recent changes made to contact fields, custom values, or the data being sent.
Steps:
1. Reopen the webhook action and double-check all dynamic fields.
2. Make sure those fields still exist and have data on the new contact.
3. Re-save the webhook step and re-test.
Question: How can I confirm my webhook is formatted correctly before going live?
Answer: Perform a validation check using a testing service.
How to Test:
- Send your payload to a mock endpoint or requestbin-style listener.
- Review the raw payload to ensure the structure matches the expected form
Question: What is the difference between a “Custom Webhook” and a “Standard” integration?
Answer: Think of a Standard Integration like a pre-built bridge (like our Google or Facebook connections). A Custom Webhook is a “DIY” bridge. It allows you to send data to any software that has an API, even if we don’t have a direct button for it. Because it is custom, you have to tell the system exactly what data to send and where to put it.
Question: Can I receive data back from the and use it later in the same workflow?
Answer: The “Custom Webhook” action is an outbound send only. If you need to send data and then receive a response to use in the next step, you would need to use a middleware tool (like Zapier or Make) or a “Custom Code” action to handle the asynchronous response.