Workflow Builder Quickstart

Build automated workflows that connect your systems and process insurance transactions—no code required, ready in 15 minutes.

What you’ll build: A workflow that receives claim data, transforms it, and prepares it for your claims system.Time to complete: 15-20 minutes

Prerequisites

Access your Liberate instance

Verify permissions

You need workflow creation permissions. If you don’t see a “Create Workflow” button, contact your administrator.

Understanding Environments

Liberate provides three environments for building and deploying workflows:

Environment	Purpose	When to Use
Preview	Development and testing	While building—test your logic here first
QA	Stakeholder validation	When ready for business review
Production	Live workflows	After validation, for real traffic

Workflows run in whichever environment you’ve selected. Always start in Preview, then QA, then Production.

Step 1: Create a Project

Projects are folders that group related workflows together.

Navigate to the left panel
Click Create Project or select an existing project
Give it a descriptive name (e.g., “Claims Intake Workflows”)

Step 2: Create Your Workflow

Click Create Workflow within your project
A Start Event Node is automatically added to your canvas

Every workflow requires a Start Event Node—this is where data enters your workflow.

Configure the Start Event Node

Click the Start Event Node to open its settings:

Execution Mode
Default Data
Manual Trigger

Choose how your workflow responds when triggered:

Mode	Behavior	Best For
Async (recommended)	Returns immediately, processes in background	FNOL intake, claims processing, policy updates
Sync	Waits for completion before responding	Real-time lookups, instant validation

Use Async for most workflows. It handles long-running processes without timeouts.

Click + Set Default workflow content to define the initial data structure.Every workflow automatically includes:

{
  "tenantId": "your-company",      // Your identifier
  "environment": "preview",         // Current environment
  "instanceId": "exec-12345",       // Unique execution ID
  "correlationId": "abc-123-def"    // Links related workflows
}

You’ll add your business data on top of these system properties.

Step 3: Add a Mapping Node

Mapping Nodes transform data as it flows through your workflow. Use them to combine fields, format values, or restructure data.

Example: Format Claimant Information

Let’s transform incoming claim data into the format your claims system expects.

Click + to add a node
Select Mapping Node
Click + Add mapping transformation

Input Data
Transformation
Output

Paste sample data to test your transformation:

{
  "claimant": {
    "firstName": "John",
    "lastName": "Smith"
  },
  "policyNumber": "HO-12345678",
  "lossDate": "2025-02-10",
  "lossType": "water_damage",
  "lossDescription": "Pipe burst in basement"
}

Write a JSONata expression to transform the data:

{
  "claimantFullName": claimant.firstName & " " & claimant.lastName,
  "formattedLossDate": $fromMillis($toMillis(lossDate), "[M01]/[D01]/[Y0001]"),
  "claimSummary": lossType & ": " & lossDescription
}

Learn JSONata syntax →

See the result in real-time:

{
  "claimant": { "firstName": "John", "lastName": "Smith" },
  "policyNumber": "HO-12345678",
  "lossDate": "2025-02-10",
  "lossType": "water_damage",
  "lossDescription": "Pipe burst in basement",
  "claimantFullName": "John Smith",
  "formattedLossDate": "02/10/2025",
  "claimSummary": "water_damage: Pipe burst in basement"
}

Merge vs. Replace

The Merge toggle controls how output is applied:

Setting	Behavior	Recommendation
Merge ON (blue)	Keeps existing data, adds new fields	✅ Use this (default)
Merge OFF	Replaces all data with output only	⚠️ Use with caution

Two-Step Save Required!

Click Save in the expression editor (left panel)
Click Save in the node settings (right panel)

If you only save once, your changes will be lost.

Step 4: Add an End Node

Every workflow needs an End Node to mark completion.

Click + to add a node
Select End Event Node
Connect it to your Mapping Node

Your workflow structure:

Start Event → Mapping Node → End Event

Step 5: Test Your Workflow

Click Preview flow in the left navigation
Paste your test data:

{
  "claimant": {
    "firstName": "Jane",
    "lastName": "Green"
  },
  "policyNumber": "HO-98765432",
  "lossDate": "2025-02-11",
  "lossType": "theft",
  "lossDescription": "Laptop stolen from vehicle"
}

Click Run flow
Monitor execution in the Logs panel

Reading the Logs

Log Entry	Meaning
✅ Green checkmarks	Node executed successfully
`***` asterisks	PII data automatically masked for security
❌ Red errors	Something failed—check the message

Run your workflow multiple times with different test data before moving to QA.

Step 6: Add External Integrations (Optional)

Task Nodes connect to external systems like your AMS, claims platform, or CRM.

Setting Up a Connection

Before using a Task Node, create a connection to your external system:

Click Connections in the left sidebar
Click Create a connection
Select the connection type (REST API, Salesforce, AWS, etc.)
Configure credentials for QA and Production environments

Example: REST API Connection

Name: Claims System API
Type: REST - Basic Authentication

QA Environment:
  Base URL: https://test-api.claimssystem.com
  Username: api_user_qa
  Password: ********

Production Environment:
  Base URL: https://api.claimssystem.com
  Username: api_user_prod
  Password: ********

Adding a Task Node

Add a Task Node to your workflow
Select your connection from the dropdown
Configure the request:

Setting	Description
Method	POST, GET, PUT, DELETE, etc.
URL	Endpoint path (appended to base URL)
Request Transformation	Map workflow data to API request
Response Handling	Where to store the response

Retry Strategy

Configure how failed requests are handled:

Strategy	Behavior
Linear	Same delay between retries (1s, 1s, 1s)
Exponential	Increasing delay (1s, 2s, 4s, 8s)
None	No retries

Set Times (retry count), Delay (milliseconds), and Status Codes to retry on (e.g., 500, 502, 503).

Validation Checklist

Before moving to QA, verify:

Next Steps

Core Concepts

Learn how data flows through workflows

Node Reference

Detailed documentation for each node type

FNOL Example

Build a complete claims intake workflow

Connections Guide

Set up integrations with your systems

Getting Started

Voice AI

Email & SMS AI

Use Cases

Integrations