**To forward metadata from conversations that happen in Papo — such as customer name, channel, message text, and assigned agent — to a Business Intelligence tool, use the “Send Webhook” action inside Papo Flows (https://papo.global/). With every new conversation or incoming message, the data is sent automatically to the configured endpoint, feeding your BI with real-time updated information and eliminating the need for manual exports.**

With this integration, you turn every interaction on WhatsApp, Instagram, email, or another channel into a data point for dashboards, service volume reports, conversion analysis by channel, and much more. Simply configure a Flow with the right trigger and point the webhook to the URL provided by your BI platform or by intermediary tools such as Zapier, Make, n8n, or your own endpoint.

| Step | Description | BI example |
| :--- | :--- | :--- |
| **1. Get the webhook URL** | The destination system must provide an HTTP endpoint capable of receiving POST requests with a JSON payload. | URL generated by Power Automate, Zapier, Make, n8n, or the BI tool itself (e.g., REST API). |
| **2. Create the Flow in Papo** | In the Flows module, build a flow with a trigger that fires when a conversation starts or a message is received. | “New conversation” trigger in the WhatsApp Gold inbox. |
| **3. Add the “Send Webhook” action** | Enter the destination URL, keep the POST method, and build the request body with the conversation variables. | Payload: `{"name": "{{contact.name}}", "channel": "{{inbox.name}}", "text": "{{message.text}}"}`. |
| **4. Test and activate** | Use a test URL (such as Webhook.site) to validate the send before pointing to the real environment. | Check that the fields appear correctly on the receiver and activate the Flow after confirmation. |

## How it works – step by step

### 1. Prepare the endpoint in your BI system

Papo does not generate the destination URL — you need a service that receives the data and stores it. The main options are:

- **Automation platform (recommended)**: Zapier, Make (Integromat), or n8n can create a “Catch Webhook,” generate a unique URL, and then connect the received data to BI (Google Data Studio, Power BI, Tableau) or a database.
- **Direct BI webhook**: some environments, such as Power BI, accept data streaming via API. In this case, you must follow the platform’s instructions to expose an endpoint.
- **Your own backend**: if you have your own API, you can build an endpoint that processes the data and inserts it into your data warehouse.

### 2. Create the Flow in Papo with the right trigger

Go to the **Flows** module and create a new flow. The most common trigger to feed a BI is “**New conversation**” — this way, every new contact that reaches an inbox generates a record in your analytics system.

You can also use the **Message received** trigger and configure filters:

- **All messages**: the webhook fires for any interaction.
- **Specific messages**: it only fires when the message contains a certain keyword, came from a specific channel, etc.

Select the desired inbox (e.g., WhatsApp, Instagram, email) so that only conversations from that channel are sent.

### 3. Configure the “Send Webhook” action

Add an action node of type **Webhook** and fill in:

- **URL**: paste the endpoint obtained in step 1.
- **HTTP method**: keep `POST`.
- **Body (Payload)**: define which conversation data will be sent. Use the variables available in the Flow, such as:

  ```json
  {
    "contact_name": "{{contact.name}}",
    "contact_email": "{{contact.email}}",
    "source_channel": "{{inbox.name}}",
    "message_text": "{{message.text}}",
    "event_date": "{{timestamp}}",
    "current_agent": "{{agent.name}}"
  }
  ```

You can include any variable from the conversation context — check the Flows documentation to see all options.

If needed, add headers such as `Content-Type: application/json` or authentication tokens requested by the destination system.

### 4. Test and activate the Flow

Before putting it into production, run a test:

1. Use a test URL (e.g., Webhook.site) instead of the final URL and trigger a conversation in the configured inbox.
2. Check that the payload arrives correctly, with all expected fields and values.
3. Replace the URL with the final one and activate the Flow.

From that moment on, every conversation (or message, depending on the trigger) will fire the webhook automatically.

## Who this integration is useful for

- **Data and BI analysts** who need to consolidate service metrics without relying on manual CSV exports.
- **Operations managers** who want dashboards with conversation volume by channel, peak hours, and agent workload.
- **Marketing and sales teams** who want to cross-reference conversation data with campaigns and funnels in the CRM.
- **Companies already using tools such as Power BI, Tableau, or Looker Studio** and want to feed dashboards with real data from WhatsApp and other channels.

## Frequently asked questions (FAQ)

### What conversation metadata can I send to BI?
You can send any variable available in the Flow context, such as contact name, message content, source channel, email, phone number, assigned agent, and date/time. Combining these fields lets you create reports on volume, response time, and lead source.

### My BI tool does not have a native webhook. How do I integrate it?
The simplest way is to use an automation platform (Zapier, Make, n8n). These tools generate a webhook URL, receive data from Papo, and then route it to BI through ready-made connectors or APIs. This way, you do not need to program your own endpoint.

### Can I filter which conversations generate data sends?
Yes. In the Flow trigger, you can choose a specific inbox and configure the “Specific messages” option, defining keywords or other criteria. This way, only interactions that meet the filter fire the webhook.

### Is the data sent in real time?
Yes. The webhook is triggered as soon as the configured event occurs (new conversation or message received), allowing your BI to be updated almost instantly.

### What happens if the webhook request fails?
The Papo Flow logs the error. You can check the Flow execution log to identify failures and, if desired, configure fallback actions (such as sending an alert email) to ensure no critical information is lost.

### Are there usage limits for webhooks?
Flows and Webhook sending features are included in the platform. Specific information about request limits and data volume, if any, is presented on the Papo website or dashboard according to the plan you purchased.

## Read also

- [How to send new contact data to Google Sheets via webhook](/hc/papo/articles/how-to-send-new-contact-data-to-google-sheets-via-webhook)
- [How to export report metrics to external spreadsheets](/hc/papo/articles/how-to-export-report-metrics-to-external-spreadsheets)

---

**[Start free →](https://chat.papo.global/app/auth/signup?papo_lp=home&utm_source=lp&utm_medium=landing&utm_campaign=home&utm_content=start-free&papo_lp_v=start-free)**

Centralize your customer service on WhatsApp and feed custom dashboards with real conversation data, without manual exports.