Workflows allows you to combine and connect different components to build anything; from a simple feedback form, to a complicated keyword text in matrix, all through a code-free visual interface.

With Workflows, you can create flows for receiving new web form entries, receiving text messages, receiving web hooks, sending emails and SMS messages and more.

Workflows empowers you to translate your unique business communication processes into an automated communication workflow. You can now easily build an automated messaging system that is completely customised to your company’s business communication processes.

Workflow Basics

A workflow consists of 2 main components:

  • Triggers

  • Actions

Triggers

Every workflow starts with a trigger, powered by provided triggers (Webform submission, Manual submission, Email or SMS received, etc), or polling a GET API call to check for new data periodically.

Triggers are how users can start automated workflows whenever they add or update something via the assigned trigger. New emails, messages, contacts, form entries, and much more are the initial data that underpin every workflow.

Current Triggers

  • New Web Form Entry

  • New SMS Received (Coming Soon)

  • Web hooks (Coming Soon)

Actions

All Workflows start with a trigger that watches for new or updated data. They get the ball rolling. Everything a workflow does with that data, though, is done by actions.

Workflow Actions push or put new data into things, like messages, or contacts or even external apps via API calls and can pass data from user customized input fields (Webforms, text ins, email ins, etc).

Action steps in Workflows can send messages, create new items or update existing items, or find existing items with search actions (which can optionally be paired with create actions to add a new item if the search does not return a result). Every action additionally returns output fields detailing what was created—and that data can be used in subsequent steps to build detailed workflows.

Current Actions

  • Conditions

  • Wait

  • Branch

  • Send Message (SMS, Email, Web)

Accessing Workflows

To access Workflow Studio, you will need to log into the new Whispir Beta Platform. You can access Whispir Beta from the below links based on your region:

Login in with Whispir credentials.

Once logged in, you will be taken to the Workflows Dashboard.

Workflows Dashboard

The Workflows Dashboard is where you go to see all of your Active and Draft workflows, as well as create new Workflows.

Each Workflow is represented by a card with information about the workflow to help you find what you are looking for at a glance:

  • An icon that represents what Triggers the workflow is using

  • The workflow name

  • Who created the workflow

  • When the workflow was last updated

  • The workflows Status

Workflow Status meaning:

  • Active: An active workflow has been published and is ready to be triggered.

  • Draft: A draft workflow has not yet been published, so cannot be triggered.

Creating a new Workflow

  1. From the Workflows Dashboard, click the Create Workflow button.

2. Name your Workflow. This can be changed at a later date.

3. Configure your selected Trigger by clicking on the Trigger Component.'

4. Once your Trigger is configured, you can start adding steps to your workflow by clicking the add step icon.

Configure the added steps as required. For detailed information on each step, click here. 

Saving and Publishing a Workflow

Saving a Workflow: Workflows does not automatically save after every change, this feature is coming soon. With that being said, we recommend saving your Workflow often while building it using the Save button in the top right hand corner.

Once a workflow is saved, you can return later and edit from where you left off.

Publishing a Workflow: To publish a Workflow into production, click the Publish button. Once published, you will be able to trigger your Workflow via your selected means with the subsequent steps running as per the rules and branches you have set.

What's Next?

Learn about:

Did this answer your question?