Vivollo
Demo

Actions reference

Find the right action for each step in a flow.

Actions are the blocks you connect in a flow. Each action does one job, such as sending a message, searching knowledge, or calling an API.

Action groups

GroupUse it for
ControlStarting, waiting, and closing a conversation
Messaging and captureSending content and collecting answers
AI and dataUsing AI and searching knowledge
Flow controlCreating branches or moving to another flow
IntegrationCalling APIs, reading and writing spreadsheets, updating connected systems
The palette in the flow editor, with the steps grouped by what they do
Every step you can add, grouped the way the editor groups them.

Actions at a glance

ActionWhat it does
Conversation openedRuns when a conversation opens before the customer sends a message
Message receivedHandles customer messages that are not waiting for another answer
InactivityContinues after the customer has been silent for a set time
Resolving / ResolvedCloses a completed conversation
Send messageSends text, options, carousels, forms, or JSON
Capture userCollects and validates name, email, or phone
Agentic AILets an assistant use tools and handle a request across several steps
Ask AIGets one response from an assistant
User intentClassifies a message and routes it to a matching path
Search documentsReturns matching records from a collection
Reply from documentsWrites an answer from matching knowledge
Get filter vocabularyReturns the available filters in a collection
ConditionalBranches using known values
Redirect to flowContinues the conversation in another flow
API requestSends an HTTP request to another system
Lookup rowsFinds rows in a connected spreadsheet
Append rowAdds a row to a connected spreadsheet
Update conversationChanges the status or metafields of a conversation
Connexease actionsUpdates assignment, customer, and conversation data in Connexease

Variables

Variables carry information between actions. Insert one with double braces:

Thanks {{customer_name}}. I found order {{order_id}}.

A value can come from the customer profile, a previous answer, an API response, an action result, or conversation memory.

Routes

A route decides which action runs next. Some actions have one route; others have different routes for success, failure, selected option, or detected intent. Always connect failure and fallback routes when they are available.