Flow blocks

Each block does one thing and continues through an exit, which on the canvas is an arrow with its name. The Add column sorts them by family —with the family color in the icon square— and Search a block finds them by name or by what they do. When you select a block, the right column shows its settings, its problems and where each exit leads.

Entry

• Start — where the flow begins. There is only one, it is born with the flow and cannot be deleted. It shows its triggers: if it has none, it tells you.

Messages

• Message — writes a message to the person and continues. Field: Text. Exits: “next” and “on failure”.
• Template — sends an approved WhatsApp template, the only way to write outside the 24-hour window. You pick the template in Approved template (you see its preview) and fill in each Parameter. If the flow can start without a conversation (from an event or the API) and you have more than one number, choose the Number that sends it. If a parameter is missing it is not sent: it goes out through “on failure”.
• Internal note — leaves a note in the conversation that only the team sees. The person does not see it and the assistant does not read it either. Field: Note text.

Questions

• Question — asks and waits for the answer. Fields: Question, Options (buttons) —each with its Option key and What the person sees—, Save the answer in (the variable name) and Time to answer (empty = the maximum, 24 hours). Each option is an exit; whatever does not match goes out through “other reply” and, if there is no answer in time, through “no reply”. Tapping a button wins over typing.

In Answer validation you choose What the answer has to be: An email, A phone number, A number, A date or Matches a pattern. If the answer does not work, it asks again (How many times to ask, from 1 to 5, with What to say if the answer doesn’t work and What to say when asking again); once the attempts run out it goes out through “not valid”.

Logic

• Condition — compares variables and continues through “yes” or “no”. Each comparison has a Variable (the name, without braces), an Operator and a Value; with several, It holds when All or Any of them hold (up to 10). There are text operators (Equals, Contains, Starts with, Is in the list, Matches the pattern…), presence (Has a value, Is empty), number (Is greater than, Is less than or equal to…), date (Is a date before, Is a date after) and format (Is a number, Is an email, Is a phone number). If something cannot be compared, it goes out through “no”.
• Depending on the value — compares one variable with a list of values, in order, and continues down the branch of the first one that matches; if none matches, through “other value”. It is the right choice when a condition would need many comparisons.
• Wait — How it waits: A length of time (How long to wait, in minutes, hours or days, up to 30 days) or Until a date saved in a variable, with a fallback time if the variable has no date. With Continue within business hours, if the wait ends outside business hours it continues when they open.
• Wait for an event — waits for something to happen to this person (a booked appointment, an appointment that could not be booked, a new contact) and continues through “happened”. You can require the event data to say an exact value and set the Maximum wait (up to 30 days); if it does not happen in time, it goes out through “no reply”.
• Business hours — continues through “open” or “closed”. There is nothing to configure.
• Split at random — splits people among Variants by their Weight, to compare two paths. The same person always lands in the same variant, and the flow saves it in the variante_<block> variable.
• Go to another flow — ends this flow and starts another one for the same person. With Pass the variables, the other one starts with everything this one collected.

Data

• Label — adds or removes a tag on the conversation (What it does: Add or Remove). You can pick one you already use or type a new one: it is created the first time it is added.
• Save variable — saves a Value in a variable, with an optional Transformation: Lowercase, Uppercase, Trim spaces, Just the number or Add days (date).
• Save to the contact — updates the contact record: Name, Email, Phone, Attributes of your own business (city, plan…) and its Contact tags. An empty field does not erase what was already there.
• Send to a webhook — notifies your systems: it sends an Event name (for example “qualified_lead”) and the Data you choose to your organization’s webhooks subscribed to the flows event (flow.event). Exits: “next” and “on failure”.

AI

• Assistant — hands the conversation to the AI assistant with What the assistant should do and, optionally, Branches it can hand control back through (each with a Branch name and When to use it). If the assistant only replies, it continues through “replied”, which is the most common case: always connect it. It has 10 minutes to finish its turn; if not, it goes out through “no reply”.

Team

• Assign — Assign to the assistant, the team queue or a person. With a person the flow has to end afterwards: once the thread belongs to someone on the team, the flow no longer writes to it. That is why the goodbye (“I am passing you to an advisor”) goes before.
• Transfer to another assistant — passes the conversation to another Assistant, with a Note for the assistant. If someone on the team has it assigned, it is not transferred.
• Close the conversation — closes it, with a Reason and, if you want, a Tag on close. After this block the flow ends.
• Snooze the conversation — takes it out of view (Snooze for a length of time). Afterwards the flow ends.
• Notify the team — sends an email with the Subject and Text you write and the link to the conversation, to the Administrators or the People you choose.

End and notes

• End — ends the flow. The conversation goes back to whoever was handling it: it is not closed.
• Note — a note on the canvas, with its Color, to explain the flow to whoever reads it. It does nothing when it runs.

Where you can use {{variables}}

A variable is written between braces —{{contacto_nombre}}— and when it runs it is replaced by its value. Every field that accepts one has a { } button that opens the list of variables: at the top, the ones that Always reach this block; below, the ones that May be empty (with the reason) and the ones that Come from outside.

• They accept variables: the Text of a Message; the Question and What to say when asking again; What the assistant should do; each Parameter of a Template; the Value of Save variable; the Name, Email, Phone and the value of each attribute in Save to the contact; the Note text of an internal note; the Note for the assistant in Transfer; the Subject and Text of Notify the team; and the value of each field in Send to a webhook.
• They name a variable, without braces: the Variable of a Condition and of Depending on the value, and the Variable with the date of Wait.
• They do not accept variables, on purpose: the Label (your catalog would end up with one tag per conversation), Assign to (what the person writes cannot choose who gets the thread), the branches’ When to use it and What to say if the answer doesn’t work, which is sent as is.

Every run starts knowing contacto_nombre, contacto_telefono, contacto_email, contacto_etiquetas, canal, flujo_nombre, ahora_fecha, ahora_hora and horario_habil. On top of that, contacto_<attribute> brings an attribute from the contact record and disparo_<field> a piece of data from whatever started the flow (for example disparo_monto when another system starts it with an amount). The rest are born in a block: Save the answer in of a Question, Save variable and Split at random.

• A variable no block saves is marked in red and blocks publishing: the gap would always come out empty.
• A variable saved in one branch but not all is marked in yellow and does allow publishing: whoever comes down the other branch will see the empty gap.
• A variable that comes from outside (contacto_…, disparo_…) gets a warning, because it depends on something the flow does not control: the contact may not have that attribute.

The limits that protect the person

• A question waits at most 24 hours; a wait or an event, 30 days; the assistant, 10 minutes per turn.
• A flow goes through up to 40 blocks in a row without waiting for anything; after that it stops, so it does not spin forever.
• The same run can go through the same block up to 25 times (a menu that asks again, for example); the 26th time it goes out through error, with the repeating block in plain sight.