Text Workflows: automate client tasks without code
Text Workflows lets you automate repetitive client support tasks with a no-code builder. Follow five steps to build your first workflow today.
Sylwia KocurUpdated 5 min readText Workflows lets you automate repetitive support tasks across LiveChat, HelpDesk, and connected apps, without writing code. As a solution partner, you can use it to cut manual work in the Text products you and your clients use. Open Workflows to build your first automation in five steps.
What are Text Workflows?
Text Workflows is a no-code automation platform that connects different apps and services to automate tasks. It allows you to create workflows that respond to events, such as a chat receiving a bad rating, and perform actions automatically instead of building custom applications. Text hosts everything for you.
Every workflow consists of two parts: a trigger (the event that initiates the workflow) and actions (the tasks it performs).
For example, when a chat receives a bad rating in LiveChat, your workflow can automatically pull the chat transcript, create a HelpDesk ticket with the details, and send a Slack notification to your support manager.
Common use cases include:
Creating support tickets when specific events occur
Routing chats to appropriate agents based on keywords or customer data
Syncing customer data between LiveChat and CRMs like HubSpot
Sending notifications to Slack when urgent issues arise
Analyzing chat sentiment with AI to prioritize responses
How do variables work?
Variables capture outputs from previous workflow steps. When an action completes — for example, “Get chat details” — it returns data you can use as variables in later steps.
To use these variables in a later step, click the {⋯} button next to any input field. Common patterns include pulling customer email from chat to create HubSpot contacts, inserting chat transcripts into ticket messages, or including ticket IDs in Slack notifications.
How do you build your first workflow?
This example creates a HelpDesk ticket whenever a chat gets a bad rating.
Create a new workflow. Go to the Workflows section, click Create workflow in the upper right corner, and choose Empty workflow.

Add a trigger. Click + Add trigger and select LiveChat from the application list. Choose Chat rated as the trigger event, then, in the trigger’s parameters, set Rating to Bad.

Pull the data you need. Click + Add action and select LiveChat again. Choose Get chat transcript as the action. This pulls the customer information you’ll need for the ticket.

Create the ticket. Click +, select HelpDesk, and choose Create ticket as the action. Fill in the ticket details with variables from the previous actions: click the {⋯} button next to an input field to insert data, such as the chat ID, customer name, or chat transcript.

Publish the workflow. Click Publish and give your workflow a descriptive name like “Create ticket for bad chat ratings.” Your workflow is now live.
What are the workflow statuses?
Workflows have three statuses:
Draft — Saves automatically when you exit without publishing.
Inactive — Workflow is disabled and won’t run.
Active — Workflow is enabled and running.
Before activation, the system validates your workflow to ensure you’ve configured everything correctly — you’ll see error indicators in any actions you need to fix.
What triggers, actions, and logic can you use?
Which triggers and actions are available?
You’ll find all available triggers and actions under + Add trigger and + Add action. Workflows supports manual triggers, scheduled triggers, and event-based triggers from LiveChat, HelpDesk, and external services like Mailchimp, HubSpot, and Slack.
Actions include built-in workflow controls (such as conditional logic, parallel execution, and delays), LiveChat and HelpDesk operations, and integrations with external services, including OpenAI for text analysis.
How do conditional paths work?
Use “if/then” statements to create different paths based on conditions. For example, you could analyze ticket sentiment with OpenAI, then route negative tickets to senior support with high priority, neutral tickets to general support, and positive tickets to a feedback collection list.
To set this up, add Conditional paths from Built-in actions, define your conditions, and add different action sequences to each branch.

How does parallel execution work?
Run multiple actions simultaneously, rather than sequentially. For example, when a high-value customer starts a chat, you could send a Slack notification to sales, create a HubSpot activity record, and tag the chat as “VIP customer” all at the same time.

How do Workflows permissions work?
Workflows inherits your permissions from each connected service. If your account has agent permissions, you can only perform agent-level actions. Admins have full access within their service scope.
When connecting external services, you’ll be prompted to authorize Workflows to access them. Once authorized, workflows run with the permissions you have for that service.
How do you troubleshoot a workflow?
You can access execution logs to view when workflows ran, which triggers activated them, which actions ran, their success or failure status, and any error messages.
What if your workflow won’t publish or activate?
Check for validation errors in action configurations.
Verify you’ve filled all required parameters.
Ensure you have proper permissions for all actions.
What if actions fail during execution?
Confirm your authentication credentials are valid.
Verify mapped variables contain expected data.
Check that external services are accessible.
What if the workflow runs but produces wrong results?
Review your variable mappings between tasks.
Check your conditional logic conditions.
Test with different input scenarios.
Frequently asked questions
Do I need coding skills to use Workflows?
No. Workflows is a visual no-code builder, so you don't need to write code to create an automation. Understanding basic logic, such as if/then conditions and variables, helps but isn't required. You build each workflow by adding triggers and actions, then passing data between steps with variables.
Can I collaborate with team members on a workflow?
Only in a limited way. Currently, workflows are visible to everyone in your organization, but only the author can edit them. Teammates can view a workflow, but any change has to be made by the person who created it, so plan who builds each workflow accordingly.
What happens if an external service is unavailable?
The workflow fails for that execution. Open the execution logs to see the failure details, then retry manually if necessary. The logs show which action failed and its error message, so you can tell whether the problem sits with the external service or with your own workflow configuration.
Can I test a workflow without affecting live data?
Yes. Use manual triggers and test with sample data, and create test accounts in the connected services so production data stays untouched. As a solution partner, you also get free demo accounts for LiveChat, ChatBot, HelpDesk, and Text, which you can use for live product demos and training.