Messaging
5 Zenvia 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.
Who they are
Zenvia sends and receives messages across the channels Brazilian customers use, from one credential and one message format. It is an official WhatsApp Business Solution Provider, so businesses reach WhatsApp through it without dealing with Meta directly. It also generates, delivers and verifies one-time codes, so an application never has to store one.
What a flow can call
/channels/whatsapp/messagesSends a WhatsApp message from a registered sender.
/channels/sms/messagesThe fallback channel when WhatsApp is not registered for the number or the template was rejected.
/channels/email/messagesEmail through the same credential and the same message shape as the other channels.
/2fa-tokensGenerates a code, delivers it over the channel the configuration names, and keeps it.
/2fa-tokens/$data.zenvia_token_id/actions/verifyChecks the code the person typed against the one Zenvia sent.
Where it sits in the decision
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 Zenvia 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.
Common questions
Add Zenvia 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 Zenvia in a decision without ever seeing the secret.
Zenvia 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.
5 operations, including “Send a WhatsApp message”, “Send an SMS”, “Send an email”. 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 WhatsApp 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.
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
Blip4 operationsBrazilian conversational platform behind much of the country's business WhatsApp.
blip.ai
SendGrid4 operationsTransactional and bulk email at scale, part of Twilio.
sendgrid.com
Slack4 operationsTeam messaging, organised around channels.
slack.com
Telegram4 operationsA messaging app with an open bot API.
telegram.org
Twilio4 operationsProgrammable SMS, voice and messaging APIs.
twilio.comReady when you are
Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.