Connect BotConversa

With BotConversa connected, Vipter sends each sale event to a BotConversa webhook, with the buyer's phone, the PIX code (PIX is Brazil's instant payment), the recovery link, the tracking and the rest of the sale data. In BotConversa, you map these fields once and build the actions for each event: send a flow, apply a tag, save a field.

Before you start, read how automations work.

Step 1: create the webhook in BotConversaCopy Anchor Link

1. In BotConversa, open Automação›Webhooks (Automation › Webhooks) and create a webhook.
2. Copy the webhook URL and keep it for step 2. Leave the screen open: you come back to it in step 3.

Step 2: connect in VipterCopy Anchor Link

1. In the Vipter dashboard, open General›Integrations›Automations›BotConversa.
2. Under Connection, fill in the field.

3. Under Events sent, uncheck what you don't want to send.
4. Leave Active — send events to this platform on and click Save.

BotConversa does not use offer rules or values per event: every event goes to the same webhook. The conditions you build there, in step 4, decide what to do with each one.

Step 3: send a sample and map the fieldsCopy Anchor Link

BotConversa only shows the fields after it receives the first delivery. The Vipter test button sends a full sample so you can map everything before the first sale.

1. In the BotConversa webhook, click Receber dados (Receive data). It starts waiting for a delivery.
2. In Vipter, click Test connection. You see Connection works.
3. Back in BotConversa, the sample shows up with all of Vipter's fields. Link the telefone field to the contact's phone and save the others you will use in custom fields, such as primeiro_nome, produto, pix_copia_e_cola, link_recuperacao and codigo_rastreio.

The sample carries evento: "teste", a phone with area code 00, which does not exist, and an example.com e-mail. No real person gets a message because of it.

The full list of fields is in the sale record.

Step 4: build the actions for each eventCopy Anchor Link

Every event arrives at the same webhook. Use the evento (or status) field in a condition to choose what to do in each case. Some examples:

To handle a product differently, add a condition on produto_id or oferta_id.

Step 5: test with a purchaseCopy Anchor Link

Open the checkout of an offer, fill it in with your e-mail and your phone and generate a PIX, without paying. Then reload the BotConversa page in Vipter.

What BotConversa receivesCopy Anchor Link

Each event reaches the webhook with the evento field (pix_generated, order_paid, checkout_abandoned…) and the status field. Use them in BotConversa conditions to pick the flow. Sales without a phone are skipped.

• The body is the Vipter sale record: fields with Portuguese names, always the same, all present in every delivery. A field with no value arrives empty.
• The phone goes in two formats: telefone, with the + and the country code (+5511988887777), and telefone_numeros, with digits only (5511988887777). Use the one your flow accepts.
• The amount goes ready for the message in valor (R$ 169,00) and as a number in valor_decimal and valor_centavos.
• link_pedido opens the order in the Vipter dashboard, for your team.

Vipter does not apply tags or fire flows on its own: the webhook actions in BotConversa do that.

Deliveries, retries and resendCopy Anchor Link

Each event shows up under Recent deliveries:

• sent: BotConversa answered with success.
• skipped: the sale has no phone. The reason shows in red: customer has no phone (BotConversa needs a WhatsApp number).
• failed: BotConversa rejected it or did not answer. If the failure is temporary, Vipter tries again on its own after 5 minutes, 30 minutes, 2 hours, 6 hours and 24 hours. If BotConversa rejects it for good, as with a deleted URL, there is no retry.

After you fix the cause, use Resend on the event's row. See retries and resend.

Common problemsCopy Anchor Link

• Enter an https:// URL

  The URL must start with https://. Copy it again from the BotConversa webhook.

• The event shows as skipped with "customer has no phone"

  The buyer did not enter a phone. Make the checkout ask for the phone. BotConversa finds and creates contacts by their WhatsApp number.

• The test worked, but BotConversa did not show the fields

  The webhook must be waiting for data when the sample arrives. Click Receber dados in BotConversa and then Test connection in Vipter.

• The event failed with 404 or 410

  The webhook was deleted or the URL changed in BotConversa. Copy the new URL, save it in Vipter and use Resend on the events that failed.

• The flow ran twice for the same sale

  A resend sends the event again, and BotConversa runs the actions again. Before you resend, check in BotConversa whether the first delivery already arrived.

What to do nextCopy Anchor Link

• See all the fields of the sale record.
• Recover carts with the abandoned checkout.
• Let the buyer know about the shipment with Mark shipping and delivery.