Skip to the operations

Messaging

Blip in a decision flow.

4 Blip operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Messaging
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Brazilian conversational platform behind much of the country's business WhatsApp.

Blip builds and hosts the chatbots that answer for Brazilian banks, retailers and utilities across WhatsApp, Instagram and web chat. Each customer gets their own endpoint, and the protocol is LIME — an envelope format rather than REST. It is where a conversation with a customer usually already lives.

What a flow can call

4 operations, each one a step you can place on the canvas.

  1. POST/messages

    Send a message

    Sends a text message into an existing conversation.

  2. POST/messages

    Send an approved WhatsApp template

    The call to use when the decision starts the conversation rather than answering one.

  3. POST/commands

    Read a contact

    Reads what Blip knows about a contact — the extras a previous conversation stored, which is often where an application id or a document number was left.

  4. POST/commands

    Write the outcome onto a contact

    Stores the decision on the contact so the bot's own logic can branch on it later without calling back.

Where it sits in the decision

Messaging calls have a natural place in a flow.

Notifying a person is part of the decision rather than an afterthought to it: the message goes out from the flow, at the point the flow decided it was warranted, carrying the same version and trace as the outcome that triggered it.

Whatever Blip returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Blip as a connection authenticating with an API key.
  • 02Blip has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Send a message” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Blip in a flow.

How do I connect Blip to a decision flow?

Add Blip as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Blip in a decision without ever seeing the secret.

Can I test Blip without touching production?

Blip exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Blip?

4 operations, including “Send a message”, “Send an approved WhatsApp template”, “Read a contact”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Send a message”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Blip be called?

Notifying a person is part of the decision rather than an afterthought to it: the message goes out from the flow, at the point the flow decided it was warranted, carrying the same version and trace as the outcome that triggered it.

Also in Messaging

Ready when you are

Wire Blip into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs