SlickText Help Center

Workflows - Objects Overview

 This guide covers the 4 different types of Workflows objects and how they connect. Before you familiarize yourself with the object types, it’s important to understand some basics about how our workflows function.

Before you can save your workflow, you’ll need to go to the basic setup tab and name your workflow, as well as select the textword it’s associated with and choose how often a contact may enter your workflow (only once ever, once at a time, multiple times). 

Once you’ve saved your first workflow, you’ll have a My Workflows page where you can clone workflows, view analytics and flush your workflow.

Connections are the lines that extend from one Workflows object to the next object or multiple objects.

  • Connections can be deleted by hovering your cursor over the connection line.

  • Connections cannot connect directly back to the object that feeds into it, as it would create an infinite loop.

Outcomes are the options available when exiting an object. Trigger and action objects will advance instantly to the next object in the workflow. Wait and Condition objects have multiple outcomes available based on the object type and settings. Any outcomes that are not connected to another object will result in the contact being ejected from the workflow.

 

Trigger Objects 

Trigger objects kick-off a workflow by inserting contacts into your workflows.  

A workflow can’t function without a trigger object. Trigger objects are actions such as joining a list, changing a contact field or starting a chat thread. 

  • Only contacts that are subscribed to the textword the workflow is attached to may enter a workflow.

  • Using multiple trigger objects may result in a single subscriber entering the workflow more than once unless you’ve limited their ability to re-enter the workflow in the Basic Setup.

Learn more about Trigger Objects

Action Objects

Action objects perform a single action. These objects execute immediately, then move the contact through to the next step.  If there is no connector to another object, the contact will be ejected from the workflow 

The only action object that behaves differently is the delay object, which will pause the workflow for a period of time, then move the contact through to the next step or eject the contact from the workflow if there is no connector to another object.

Action objects that send messages can use merge tags to insert the contact’s information into the message. Click here to learn more about merge tags.

Learn more about Action Objects

Condition Objects

Condition objects run a status check based on the condition the object has been programmed to check for. 

  • These objects execute immediately. 

  • Most condition objects have yes/no outcome options, though some condition objects have more than two outcome options.

  • Outcomes that are not connected to another object will eject the contact from the workflow unless additional condition objects are checking to see if the contact matches another property.

Learn more about Condition Objects

Wait Objects

Wait objects pause the workflow until a condition is met or a period of inactivity elapses.

These objects allow for a conversational flow and prevent the contact from advancing until they’ve taken action or the wait time has expired. 

  • Once configured, some wait objects have more than two outcome options.

  • Outcomes that are not connected to another object will eject the contact from the workflow.

Learn more about Wait Objects

You're in excellent hands. We work with some of the world's greatest companies.

United Airlines Cintas FedEx Lyft General Electric Hyatt