Getting started with automated workflows
  • 09 May 2021
  • 2 Minutes to read
  • Dark
  • PDF

Getting started with automated workflows

  • Dark
  • PDF

This article introduces Lightico automated workflows.

🎦 Watch related video:

About automated workflows

With the Lightico Workflow tools, you can build and design automated workflows that bring together the different Lightico elements into one unified customer interaction. Complex business logic and conditions can be built into these workflows, allowing you to determine the steps in the flow based on inputs by customers, agents, or an API. 

In a single workflow, customers can complete a form, submit a document, read a dynamic text and sign a document. All the steps are tailored to their needs, based on previous inputs. 

You design the different elements of the flow, such as the form and the dynamic documents, using the relevant workflow tools. You then drag and drop the elements onto a canvas and define the conditions and business logic in the UI, without the need to enter any code. 

Automated workflows allow customers to experience a seamless, customized interaction and allows business administrators and agents to follow a streamlined, compliant process with very little room for error.

Workflow example

Assume that you are creating a workflow to help agents close a deal with their customers. In this example, the customers need to first authenticate themselves by submitting a photo ID. They then fill out some personal details in a form. Due to state law, if they live in California, they need to agree to the terms and conditions. In the last step, they sign the final agreement. 

The following example in the workflow designer, incorporates all of these steps:

Step 1: Customer authenticates

The customer submits a photo id and the document goes through an automatic authentication process.

Step 2: Condition based on authentication result

  • If the photo id is authenticated, the customer moves to the next step.
  • If the authentication fails, the customer cannot proceed and the workflow ends.

Step 3: Customer fills out a form

The customer fills out their personal details.

Step 4: Condition based on customer address

  • If the customer lives in California they are taken to a terms and conditions page (step 5).
  • If the customer lives anywhere else, they skip the terms and conditions step and sign the agreement (step 6).

Step 5: Customer reads Terms and Conditions

Customers living in California see the terms and conditions and need to select a checkbox to show that they agree to the terms.

Step 6: Customer signs agreement

In this final step, all customers sign the final agreement. The personal details on the agreement are automatically filled in based on the information that was provided in the form in step 3.

Workflow elements

Workflows are made up of multiple elements that are brought together in the workflow designer. Before you create your workflow, you need to build each one of those elements that will form the building blocks of the workflow. This section describes each of those elements. 


Attributes are the core building blocks of automated workflows. They are built into the different elements, such as forms and documents, and they form the basis of the workflow conditions and logic. For more information, see Understanding attributes.


Forms are used to capture customer information during a workflow. For more information, see Create forms

PDF (Template-based document)

PDF template-based documents can be incorporated into a workflow for customers to approve or sign. For more information, see Create PDFs for workflows.

Dynamic documents

In dynamic documents, you can incorporate conditions and business logic to determine the way the document appears to your customers. For more information, see Create dynamic documents.

Workflow designer

After you have created the necessary elements, you design your workflow in the workflow designer, which includes condition tools such as the switch and condition hub. For more information, see Create workflows.

Was this article helpful?

What's Next