Use the automation workspace to manage workflows that carry out tasks in the background. A workflow follows the steps you configure and can run without an active customer conversation.
Open the automation workspace
-
Open the profile selector at the top left of HALO Studio.
-
Select Automations Workspace.
-
Open Workflows.
If your subscription includes only automations, HALO Studio opens this workspace directly and does not show the profile selector.
The workspace is provided for your account. You do not create it through the profile creation form, and you cannot rename or delete it.
Work on a workflow
Open an existing workflow to edit its steps, or use Add new workflow to start a new one. Its name and description help your team find it when connecting it to other work on the CM.com platform.
A workflow needs a trigger to run. This can come from another system, such as your customer data platform (CDP), or from a conversational tool in HALO.
The step picker shows the steps available for this workspace. Steps that require another CM.com application also depend on your account's access to that application.
The automation workspace does not contain conversational agents, knowledge sources, or conversation history.
What to expect
Saving a workflow keeps your changes in Studio. Publish the automation workspace to make those changes available to live runs. Until then, an existing workflow continues to use its published version.
A conversational tool that starts your workflow can only be published after the workflow has been published. You configure that connection with the Trigger workflow step in the conversational tool.
Open Analyse to review workflow runs. Select a workflow, then open a run to inspect its steps, status, and any errors. For runs started by a conversation, you can follow the link back to that conversation.
A run appears in analytics after it finishes or pauses. It can take a few minutes to appear.
If you tested a conversational tool in the debugger, its Trigger workflow step checks the setup but does not start a workflow. Test the workflow itself to inspect its steps.
For workflow step instructions, including waiting, reading CDP data, and sending campaigns, see Step availability.