To test a Papo (https://papo.global/) webhook connection before activating automation, you can use an external tool such as Webhook.site to validate the destination URL, check the JSON payload format, and fix sending errors without affecting real contacts. This process works both for native account webhooks and for the “Send Webhook” action inside Automation Flows.
Early validation prevents a broken integration from losing data or interrupting customer journeys. With a temporary test URL, you can inspect exactly what Papo is sending — headers, body, and response codes — and make adjustments before pointing to the final system.
Test process summary
| Step | Action | Tool / location |
|---|---|---|
| 1. Get a test URL | Go to webhook.site and copy the generated URL. | Webhook.site |
| 2. Configure the webhook in Papo with the test URL | Enter the URL in the webhook destination field (in the Integrations section or in the Flow action). | Papo dashboard |
| 3. Trigger the webhook | For account webhooks, send a WhatsApp message to the connected inbox. For webhooks in Flows, enroll a test contact in the flow. | Inbox or Flow |
| 4. Analyze the received payload | In the Webhook.site dashboard, view the request that arrived: method, headers, and the JSON body. | Webhook.site |
| 5. Fix and replace with the production URL | If the payload is correct, replace the test URL with your system’s real URL and activate the automation. | Papo dashboard |
How to test account webhooks (Integrations)
Papo native webhooks trigger on every new message received in an inbox. To validate them without risk:
- In the Papo dashboard, go to Settings > Integrations > Webhooks and create a new webhook.
- Set the trigger — for example, All messages — and in the URL field, paste the temporary Webhook.site address.
- Save the webhook.
- Send a test message (via WhatsApp or another connected channel) to the monitored inbox.
- In Webhook.site, refresh the dashboard and find the newly arrived request. Check the JSON body: it should contain data such as sender number, message content, and conversation ID.
- If the JSON is empty or malformed, review the chosen trigger and confirm that the message was actually received by the inbox.
- After validating, edit the webhook and replace the URL with your destination system’s URL.
How to test the “Send Webhook” action in Automation Flows
Inside the Flow editor, the Send Webhook action lets you trigger data at a specific step in the journey. Test it with a temporarily active flow and a control contact:
- Build the Flow and add the Send Webhook node at the desired point.
- In the node configuration panel, fill in the URL with the Webhook.site address, choose the POST method, and build the JSON body using Papo variables such as
{{contact.name}}and{{contact.phone}}. - Activate the Flow.
- In the CRM, manually enroll a test contact in this flow (following the same procedure as testing Automation Flows).
- Monitor the Flow execution history and, at the same time, watch Webhook.site.
- The received request should show the JSON with the test contact’s real values, replacing the variables. If not, check the body (use
"name": "{{contact.name}}"and make sure the contact has the fields filled in). - If the request returns a 4xx or 5xx error, check whether the method is correct (usually POST) and whether the
Content-Type: application/jsonheader was included. - After validation, deactivate the Flow, replace the destination URL with the production URL, and activate it again.
Who this process is for
- Administrators and system analysts who need to ensure integration integrity before releasing them.
- Teams building Flows with webhooks for CRMs, spreadsheets, or automation tools and want to debug the payload without impacting real leads.
- Any user who customizes account webhooks and wants to confirm that events are being sent correctly.
Frequently asked questions
Can I test the webhook without sending a real message?
Not for account webhooks, because they are triggered by inbound messages. Use a test WhatsApp number (your own or a colleague’s) to generate the event. For Flows, manually enrolling a control contact allows testing without the lead being a real customer.
Is Webhook.site free? Should I use it in production?
Yes, Webhook.site generates temporary public URLs and shows traffic in real time, ideal for debugging. Never use these URLs in production — after testing, replace them with your destination system’s URL.
The webhook fired but the payload is empty. What should I check?
For account webhooks, check the trigger (whether it is capturing the correct message type) and the inbox permissions. For the Flow action, review the variables in the body — fields such as {{contact.name}} will only be filled if the contact has the name field registered. Test with a contact that has complete data.
How do I fix 401 (unauthorized) or 403 (forbidden) errors?
These errors indicate that the destination system rejected the request. Add an authentication header (for example, Authorization: Bearer your-token) in the Headers field of the webhook configuration, as directed by the external tool’s documentation.
Can I test Kanban webhooks the same way?
Yes. Webhooks configured in the Kanban module can be tested with a temporary Webhook.site URL — just move a card from one column to another (an action that triggers the event) and inspect the payload in the test dashboard.
Do I need to keep the Flow active to test the webhook?
Yes. Only Flows with Active status process the webhook node. Activate the flow, run the test, and then deactivate it if necessary.
Read also
- How to test an automation Flow before activating it
- How to send new contact data to Google Sheets via webhook
With the first user free, you can already create webhooks and test integrations with no commitment.