To integrate your automated processes with other systems, Papo (https://papo.global/) allows the use of the "Send Webhook" action within Automation Flows. With this feature, you can send real-time contact data to external platforms, such as your CRM, spreadsheets, or automation tools (like n8n and Zapier), whenever a contact reaches a specific stage in your flow.
The Webhook action acts as a communication bridge, sending an automatic notification from one system (Papo) to another. This opens up a range of possibilities for creating connected work ecosystems, where information flows without the need for manual data export and import. For example, you can register a new lead in your main CRM the exact moment they are qualified by your chatbot on WhatsApp.
| Configuration Parameter | Description | Usage Example |
|---|---|---|
| Webhook URL | The address (endpoint) of the external system that should receive the data. | URL provided by a system like n8n, Zapier, or your own backend. |
| HTTP Method | The way data will be sent. POST is the most common for sending data. |
Select POST to send information in the request body. |
| Body (Payload) | The data you want to send, usually in JSON format, using Papo variables. | {"nome": "{{contact.name}}", "email": "{{contact.email}}", "telefone": "{{contact.phone}}"} |
| Headers | Additional information for the request, such as content type or authentication keys. | Content-Type: application/json |
How to configure the Webhook action step-by-step
Integrating an external system via a Webhook in a Papo Flow is a technical but straightforward process. Follow the steps below to configure data sending.
1. Add the "Send Webhook" node to your Flow
Within Papo's visual Flow editor, at the point in the journey where you want data to be sent, add a new action node. Find and select the "Send Webhook" action. This node will be responsible for triggering communication to the external system.
For example, you can add this node right after a contact answers a qualification question or at the end of a welcome sequence.
2. Configure the Destination URL
In the Webhook node's configuration panel, the first field to fill is the Webhook URL. This is the unique URL provided by the system that will receive the data.
- Where to find this URL? You should obtain it from the documentation or dashboard of your external system (e.g., your CRM, ERP, or an automation tool like n8n). Tools like Webhook.site are also great for generating temporary URLs for testing.
3. Choose the HTTP Method
You will need to choose the method for the request. The most common are:
- POST: Recommended for most cases. It allows sending a larger volume of structured data in the request body (payload). It's ideal for creating or updating records in other systems.
- GET: Used to request data from a server. Data is sent as parameters in the URL itself. It's less common for this type of integration, as it's less secure and limited in size.
Select POST to send your contact's data.
4. Assemble the Request Body (Payload)
The body (or "payload") is where you define which contact information will be sent. Papo allows you to use dynamic variables to insert the data of the contact passing through the Flow.
The most commonly used format is JSON (JavaScript Object Notation). In the body configuration field, you can assemble a structure like this:
{
"nome_completo": "{{contact.name}}",
"email_contato": "{{contact.email}}",
"telefone": "{{contact.phone}}",
"etiqueta": "Novo Lead Qualificado",
"origem": "Flow de Boas-Vindas"
}
In this example:
{{contact.name}},{{contact.email}}, and{{contact.phone}}are variables that Papo will automatically replace with the contact's real data.- "etiqueta" (tag) and "origem" (origin) are fields with fixed values that you can add to provide context for the information in the destination system.
5. Test and Activate the Flow
Before activating your Flow for all contacts, it's crucial to test the integration.
- Use a test URL (like Webhook.site) to verify that data is being sent correctly and in the expected format.
- Enroll a test contact in your Flow and observe if the Webhook is triggered and if the external system receives the information.
- After confirming that everything is working, replace the test URL with your system's production URL and activate the Flow.
Frequently Asked Questions (FAQ)
What is the difference between a Webhook and an API?
Simply put, a Webhook is a "push" mechanism. Papo sends data to your system automatically when an event occurs. An API query, on the other hand, is a "pull" mechanism, where your system actively requests data from Papo. Webhooks are ideal for real-time notifications.
How do I get the URL for my Webhook?
You need to generate this URL in the system that will receive the data. Consult the documentation of your CRM, ERP platform, or automation tool (like n8n, Zapier, Make) to find the "Webhooks" or "API" section and create a new receiving endpoint.
What contact data can I send via Webhook?
You can send all standard contact data stored in Papo, such as name, phone, email, as well as custom fields and tags you have configured. Use variable syntax (e.g., {{contact.field_name}}) to dynamically insert this information into the request body.
What happens if the external system is offline when the Webhook is sent?
If the destination system does not respond or returns an error, the Webhook delivery will fail. Papo will attempt to send the notification, but guaranteed receipt depends on the availability and correct configuration of the receiving system. It's important to ensure your webhook endpoint is stable.
Can I send data securely?
Yes. Webhooks operate over the HTTPS protocol, which encrypts data in transit. For an extra layer of security, many systems allow the use of authentication keys (tokens) in the request headers, which you can also configure in Papo's "Send Webhook" action.
Besides contacts, can I send other information?
Yes. Although the most common use case is sending contact data, you can structure your Webhook's payload to include any static or dynamic information available in the Flow's context, such as the Flow's name, the answer to a specific question, or the event date.
Create your account and explore Automation Flows to connect your processes.