Saltar al contenido principal

Automation actions, integrations and data tables

The steps on this page make an automation do something: send a message, write into your CRM or helpdesk, book an appointment, keep a list, call someone back. Decisions, waits and approvals are on Automation logic, approvals and notifications; what starts an automation is on Automation triggers and limits.

Every step takes its values from templates such as {{trigger.caller}}, {{vars.note}} or {{nodes.lookup.name}}. A value is escaped for where it lands: a message gets plain text, an address gets URL encoding, and a phone number is turned into international format (+525512345678). A step that cannot build its values (for example a "phone number" that is not one) takes its error exit.

Every step has a next exit and an optional error exit. In an automation, a step that fails without an error exit ends the run as failed; in a call flow it takes next, so a caller is never left waiting.

Messages​

StepWhat it doesNeeds
Send SMSSends a text from one of the company's SMS numbers. The SMS caps of the company, the number and the user apply, and a recipient who answered STOP is never messaged (the step fails with MPBX-FLOW-OPTED-OUT).An SMS number
Send WhatsAppSends free text while the customer's last message is less than 24 hours old, and an approved template (name, language and the values of {{1}}, {{2}} ...) otherwise. Fill in the text, the template, or both: with both, the text goes out inside the 24-hour window and the template when the window is closed. With text only, a customer whose window is closed is not messaged (the step fails with MPBX-FLOW-ACTION-FAILED). The step's output mode says which one was sent (text or template). A reply to a message the customer just wrote always has an open window.A WhatsApp channel
Send e-mailSends one e-mail (one recipient, subject and text) through the company's mail provider.A mail provider
Post to team chatPosts into a team chat group room, shown as a message of the company's automations. Members see it live and get the usual chat notifications.A group room
Post to Slack / Post to Google ChatPosts into a channel or space of the company's Slack or Google Chat integration (the channel names are the ones mapped in that integration).The integration
Post to Microsoft TeamsPosts into a Teams channel through a Teams workflow ("When a Teams webhook request is received"). Keep the workflow address as an HTTP secret of the automations and pick that secret in the step; the address is never stored in the flow.An HTTP secret
Send webhookSends a signed Standard Webhooks message (webhook-id, webhook-timestamp, webhook-signature) with your event type and fields to an https address on the company's host allow-list. Pick an HTTP secret to sign with (a whsec_... secret, or any text).Optional HTTP secret

A message is never sent twice. Before the provider is asked, the send is recorded. If a step is retried or a run resumes after a restart, a send that went out is not repeated (the step takes the recorded result), and a send whose outcome is unknown (the provider stopped answering) is not tried again: the step fails with MPBX-FLOW-SEND-UNCERTAIN. A webhook keeps the same webhook-id on every attempt, so the receiver can drop a repeat. One run sends at most 50 messages and other one-time actions.

Send SMS, Send WhatsApp, Send e-mail and Post to team chat also work in call flows (for example "text the caller our address"). There they have at most 5 seconds and one retry.

CRM, helpdesk and calendar​

These steps use one of the company's integrations. The step names one of the company's integrations; the flow designer offers only those that can do what the step does (the list comes from GET /api/v1/flows/node-catalog). Its credentials stay with the integration: a flow never holds a password or a token.

StepWhat it does
CRM: look upFinds the contact of a phone number. Outputs found, name, url and the details. Works in call flows too (for example to greet a known customer or route them).
CRM: add noteAdds a note to the contact of a number.
CRM: create lead, create contact, create task, update dealCreate or change records, where the connected system offers it (a field service system's "job" is a task; a marketing tool's audience entry is a lead). Kommo, Bitrix24 and Odoo offer all four, see the table below.
Helpdesk: open ticket, add comment, look upOpen a ticket, add an internal note to a ticket, find a customer by phone, e-mail or name. Look up works in call flows too.
Calendar: find slots, book, cancelRead the free slots of a scheduling account, book one, or cancel a booking that an automation or an AI agent made. The double-booking check of the scheduling integration applies. Besides scheduling accounts you can pick one of the AI assistant's calendars (Google Calendar or Microsoft 365, see AI tools, connectors and knowledge): the steps then use its opening hours, notice and booking horizon, the double-booking check reads the provider's calendar again right before it writes, and a cancel needs the booking's reference and the phone number or name the customer gave. The automation stands in for the customer's spoken yes. Find slots outputs slots, the start of each free slot, which Book takes as start.

CRM writes on Kommo, Bitrix24 and Odoo​

The native connectors sign in with the connection you made on the Integrations page (OAuth for Kommo and Bitrix24, an API key for Odoo) and write with the same permissions, so nothing about a connection is stored in the automation. The values of the args of each step:

StepValuesWhat happens
Create contactname (required), phone, email, companyCreates the contact. When the phone number already belongs to a contact, nothing is created and that contact is returned (created is false), so a retried or repeated automation never makes a duplicate. Kommo needs a phone number or an e-mail address.
Create leadphone (required), nameCreates a lead for the number (Kommo links it to the contact of that number, or creates one).
Create tasknumber, title (required), text, due_at (a date and time such as 2026-12-01T10:00:00Z; default: tomorrow)Creates a task on the contact of that phone number (a to-do activity in Bitrix24 and Odoo). Nothing is created when the CRM does not know the number (created is false).
Update dealdeal_id, or number for the first open deal of that phone number; then name, stage (the stage's id; Bitrix24 uses its stage codes such as C1:WON), amount (a whole number) and noteChanges only what you fill in and adds the note to the deal. Nothing changes when the CRM has no such deal.

A step that cannot do its job (the CRM refuses, the sign-in expired) takes its error exit.

What each integration needs (the fields of a note, a ticket or a booking) is shown in the step as soon as you pick the integration, and the values are checked before they are sent. A step whose integration is removed, fails its connection test or does not offer what the step does fails with MPBX-FLOW-INSTALL-UNSUPPORTED until you pick another one or fix the integration.

Data tables​

Data tables are small spreadsheets the company keeps for its automations: a call-back list, leads from a campaign, opening exceptions, a list of VIP numbers. Create and manage them through the API (/api/v1/flows/tables, see the API reference); the flow designer offers them in the table steps.

  • A table has 1 to 20 columns. Each column has a name (a-z, digits and _) and a type: text, number, true/false, phone (stored in international format, so 55 1234 5678 and +52 55 1234 5678 match) or date and time.
  • A table holds up to 100 000 rows; a company can have up to 50 tables. A value is at most 1000 characters. When a limit is reached, new rows are refused; nothing is ever deleted for you.
  • Export downloads the whole table as CSV. Values that a spreadsheet would run as a formula (starting with =, +, - or @) start with an apostrophe in the file.
  • A table that a live flow uses cannot be deleted. Table changes and exports are recorded in the activity log.
StepWhat it doesOutputs
Table: add rowAdds a row with the values you map to columns. A retried step adds its row once.row_id, row
Table: find rowFinds the first row whose column has a value. Works in call flows too (for example "is this caller on the VIP list?").found, row_id, row
Table: update rowsChanges the rows (up to 100) whose column has a value; with add when missing it adds a row when none matches.updated, row_id

Calls​

StepWhat it does
Click to callRings someone first; when they answer, the number is dialled through the dial plan. Pick a user (their phones ring; the number is dialled as that user, with their calling permissions) or enter the extension number of a ring group or queue in ring first (every member's phones ring at once, or the ring group's own order; for a queue, the agents who are logged in; the first to answer is connected). The customer is then dialled as the ring group or queue, with that extension's outbound rules, calling profile and call limits, so a number the group may not call is refused. A queue nobody is logged in to fails the step. Use it to call a lead back the moment a web form arrives.
Outbound AI callQueues a call of one of the company's outbound AI call campaigns. The campaign's calling hours, retries and do-not-call list apply; a number on the do-not-call list is refused (MPBX-FLOW-OPTED-OUT). A retried step queues the call once.

AI steps​

AI steps use the company's own AI model. They run on the Automation AI feature in AI setup: until you save a setting for it, they use your call summary model and its switch. Everything the step reads (a transcript, a voicemail, a message) is treated as data, never as instructions, and the AI has no tools, so a caller cannot make a step do anything else. Usage and cost are counted, and a used-up AI budget stops the step (it takes its error exit; the error is MPBX-AI-BUDGET).

StepWhat it doesOutputs
SummariseA short summary of a text (up to 6 sentences), optionally in a language and with a focus ("next steps and who must act"). Automations only.summary
ClassifyPicks one of up to 12 labels you describe, or other when none fits. Branch on the result with a Switch step. Works in call flows too.label, confidence
Extract fieldsFills up to 16 fields from a text. Each field has a type: text, number, yes/no, phone, e-mail, date or one of a list of values. Every value is checked: one that does not fit is empty and listed in missing. Save a field with the name fields.<name>. Works in call flows too.fields, missing
TranslateTranslates a text into English, German, Spanish, French, Italian, Japanese, Portuguese, Russian or Chinese. Automations only.text, source_lang
Draft textWrites a short message (up to 1000 characters) from your instructions and a text, for example before Send SMS or Send e-mail. A draft has no link unless you allow links, never a one-time code or password, and never mentions the AI. A draft that fails these checks takes the error exit instead of being sent. Automations only.text
AI assistCall flows only. Turns on live assist for the person who takes the call next, even when their queue has not switched live assist on (the company's live assist switch and provider are still needed).none

After the call​

A call flow can end with an after-call hand-off: pick an automation and the call's variables to pass on. About 15 seconds after the call flow ended (10 minutes when it handed the call to people, because the call goes on), the automation starts once with those variables and the call's details (trigger.call.caller, called, answered, end). The automation must start with Run now (a manual trigger) and declare the variables it wants as inputs; variables it does not declare are dropped. This is how a call flow sends a follow-up (for example "SMS the caller a summary of the next steps") without holding the call.

Saving outputs​

Every step publishes its outputs as nodes.<step>.<output> for the steps after it. With save you also copy an output into a variable, for example the CRM name into vars.caller_name. In call flows saved values keep the call flow character set.

Retries​

In an automation, a step that fails in a way that may pass (a network problem, a busy provider, a rate limit) can be retried up to 5 times, with a fixed or growing pause. In a call flow at most one retry is allowed, within the step's time limit. Messages and other one-time actions are still never repeated.