Connect ManyChat

With ManyChat connected, every Vipter sale event finds the buyer's contact in ManyChat, or creates a new one, fills in the custom fields you created, applies the tags and fires the flow you chose for that event. For example, a generated PIX (Brazil's instant payment) can become the pix-pendente tag and a reminder flow with the copy-and-paste code.

Before you start, read how automations work.

Step 1: generate the API token in ManyChatCopy Anchor Link

1. In ManyChat, open Settings›API.
2. Generate a token and copy it. It has the format 1234567:a1b2c3….

Step 2: create the custom fields in ManyChatCopy Anchor Link

Vipter fills in the ManyChat custom fields that have the same name as a field of the sale record. In ManyChat, create only the ones your flows will use. The most common:

The name must be the same, and upper or lower case does not matter. A field that does not exist in ManyChat is not sent, and an empty value does not erase what the field already has. A value that does not fit the field's type is also left out: valor in a Number field, for example. For numbers, use valor_decimal.

Step 3: connect in VipterCopy Anchor Link

1. In the Vipter dashboard, open General›Integrations›Automations›ManyChat.
2. Under Connection, fill in the numbered fields.

3. Under Tags and flows per event, enter what each event does in ManyChat. See the format right below.
4. Under Events sent, uncheck what you don't want to send.
5. Leave Active — send events to this platform on, click Save and then Test connection.

How to write the tags and the flowCopy Anchor Link

Each field accepts tag names separated by commas and, to fire a flow, flow: followed by the flow code. The code is the end of the flow's address in ManyChat, such as content20241001120000_123456.

A tag that does not exist yet in ManyChat is created on the spot. Events without a value of their own use the Default tags and flow. With no value at all, the contact and the fields are still updated, which is already enough for a ManyChat rule that fires when a field changes.

Step 4: use tags and a flow per offer (optional)Copy Anchor Link

Do this step when a product needs a tag or a flow of its own.

1. Under Tags per offer, pick the Offer.
2. Enter the Tags and flow, such as curso-x or curso-x, flow:content20241001123000_678901.
3. Click Add rule.

The rule's tags are added to the event's tags. If the rule has a flow:, that flow starts instead of the event's flow. The rule applies to every event of the offer, and also to the other offers of the same product. For example: with pix-pendente, flow:…_123456 on PIX generated and the curso-x rule on the offer, a PIX generated for Curso X gets the pix-pendente and curso-x tags and fires the PIX flow.

What happens on each eventCopy Anchor Link

1. Contact: Vipter looks up the contact by phone and then by e-mail. If it finds none, it creates a contact with the name, the WhatsApp number and the e-mail. The e-mail goes in without marketing consent, because the checkout does not collect that consent, and the number does not go in as SMS. An existing contact keeps its name and permissions.
2. Fields: the custom fields named after a Vipter field receive the event's values.
3. Tags: the event's tags, plus those of the offer rule.
4. Flow: the offer rule's flow, if it has one, or the event's flow.

The fields come before the flow, so the flow's message already shows the PIX code or the tracking. Tags are never removed: use refund or cancellation tags in your ManyChat automations.

Deliveries, retries and resendCopy Anchor Link

Each event shows up under Recent deliveries:

• sent: contact found or created, fields, tags and flow applied. A field that ManyChat rejected does not change the status: the delivery still counts as sent.
• skipped: the sale has no phone and no e-mail (customer has no phone and no e-mail).
• failed: a step failed. The reason starts with the step's name, such as addTagByName "cliente", sendFlow … or createSubscriber. Temporary failures, such as ManyChat being down or a rate limit, get automatic retries. A rejection from ManyChat, such as a flow that does not exist, is not repeated.

After you fix the cause, use Resend. See retries and resend.

Common problemsCopy Anchor Link

• The platform refused the credentials with "this ManyChat account is not Pro"

  The ManyChat account is not on the Pro plan. The API only works on Pro.

• The custom field was not filled in

  Check that the name matches the Vipter field, such as pix_copia_e_cola, and that the type accepts the value. The field also stays as it is when the event does not have that data: a generated PIX has no tracking, for example.

• The delivery failed at sendFlow

  The flow code is wrong or the flow is not published. Copy the end of the flow's address again and check the flow: in the event's or the rule's value.

• The delivery failed at createSubscriber saying the contact already exists

  The contact exists in ManyChat with WhatsApp only, and the phone lookup did not find it. Check that the number in ManyChat has the country code. Then use Resend.

What to do nextCopy Anchor Link

• See all the fields of the sale record.
• Understand values per event and offer rules.