Introduction to Experience and Workflow Studio
Complete overview of the Flow Builder
Actions are nodesInsert Definition Here that execute the subsequent steps after a triggersInsert Definition Here. These are nodes that execute subsequent steps, guiding the customer through a journey or handling data processes. Actions in the Flow Builder can be broadly categorised into messaging, data, and workflow nodes.
Messaging nodes
These nodes are responsible for sending communications to recipients. Each messaging node can be configured to send a specific message and, where applicable, respond based on customer interactions.
Outbound SMS
Sends a single SMS to a designated recipient. The node offers two outcome paths based on message delivery status—sent and not sent. Handle fallbacks and failures by tailoring experiences based on these outcomes.
Conversation
Handles two-way SMS interactions, enabling conversations that can adapt based on customer responses. Lumary’s Engagement Console industry-leading intent matching capability provides the user the ability to listen for any customer reply based on flexible rules, ranging from simple keywords to complex pre-built logic.
Outbound Email
Sends emails, which can be personalised and scheduled as part of the flow. Emails can be either built from scratch using email design pane or from importing HTML code.
Data nodes
Data nodes handle the flow's interactions with external data sources. This includes sending data to and receiving data from external APIs, allowing the flow to integrate seamlessly with other systems. These nodes are crucial for workflows that rely on dynamic data exchange.
Make a web request
Interacts with external services and APIs, allowing the flow to send data to or receive data from outside sources. It can be used to update a CRM record, log an event, or enrich the experience with external data.
Read more about integration-specific data nodes in the Integrations Hub.
Workflow nodes
Workflow nodes introduce logic and decision-making capabilities into the flow. These nodes ensure that the flow adapts and responds to varying inputs and scenarios.
Criteria Filter
Filters customers or data points based on predefined criteria, ensuring that only the relevant individuals or data proceed to the next step.
Criteria Split
Diverges the flow into different paths, each tailored to a specific customer segment or scenario.
Reporting Point
Marks a specific point in the workflow for reporting purposes, allowing for the collection of data on the flow’s performance.
Setting up an action
- Choose the appropriate action node from the Flow BuilderInsert Definition Here based on what needs to be accomplished in the subsequent steps following a trigger.
- Configure the node with the necessary details, whether it’s crafting a message template, defining API request parameters, setting criteria for filtering or splitting, or establishing timing for delays or reporting.
- Use any subsequent nodes to ensure a seamless flow of the automated workflow.
Action nodes execute in a predefined sequence, as determined during in the flow. This sequential execution allows for complex workflows that can adapt based on dynamic inputs and conditions. Action nodes offer the capability to integrate with various systems and services, enhancing the flow's utility and adaptability.