Skip to main content

​
The Workflow Builder

The workflow builder is a visual canvas where you design automation pipelines by adding and connecting nodes. [SCREENSHOT: Workflow editor canvas showing a complete workflow with multiple node types] Caption: The workflow builder lets you visually design automation pipelines

​
Creating a New Workflow

1

Navigate to Workflows

Go to Workflows from the main navigation (admin only).
2

Click New Workflow

Click the “New Workflow” button in the top right.
3

Choose a Starting Point

Select from:
  • Blank workflow - Start from scratch
  • Template - Pre-built workflows for common use cases
[SCREENSHOT: Template picker showing available workflow templates] Caption: Choose a template or start from scratch
4

Name Your Workflow

Give it a descriptive name like “Enterprise Deal → CSM Assignment” or “SMB Onboarding Flow”.

​
Working with the Canvas

​
Adding Nodes

From the sidebar:
  1. Click the ”+” button or open the node palette
  2. Drag a node type onto the canvas
  3. Drop it where you want it
From existing nodes:
  1. Hover over a node’s output handle
  2. Drag to create a connection
  3. Release to open the node picker
[SCREENSHOT: Node palette showing all available node types grouped by category] Caption: The node palette groups nodes by category for easy discovery

​
Connecting Nodes

  • Drag from output to input - Create connections between nodes
  • Click a connection - Select it for deletion
  • Press Delete/Backspace - Remove selected connection
Nodes automatically validate connections. You can’t connect incompatible node types.

​
Selecting & Editing Nodes

  • Click a node - Select it and open the properties panel
  • Double-click - Open detailed editor
  • Drag a node - Reposition it on the canvas
  • Delete key - Remove selected node

​
Node Types Reference

​
Trigger Nodes

Purpose: Entry point that defines when the workflow triggersConfiguration:
  1. Select CRM provider (HubSpot, Salesforce, or Notion)
  2. Configure trigger conditions:
    • HubSpot: Select pipeline and stage
    • Salesforce: Select opportunity stage
    • Notion: Select database, status property, and trigger values
Output: Account data, CRM snapshot, contacts[SCREENSHOT: Start node editor showing HubSpot pipeline/stage configuration] Caption: Configure which CRM events trigger this workflow
Only connected CRM integrations appear as options. Connect your CRM in Connectors first.

​
Logic Nodes

Purpose: Branch workflow based on Yes/No conditionsConfiguration:
  • Select a variable to check (ARR, segment, custom field)
  • Choose comparison operator (equals, greater than, contains, etc.)
  • Set comparison value
Outputs: Two paths - “Yes” (condition true) and “No” (condition false)Example use cases:
  • Route high-ARR accounts differently
  • Check if customer is in a specific segment
  • Verify required fields are present
[SCREENSHOT: Condition node editor with ARR comparison configured] Caption: Branch based on account data like ARR or segment
Purpose: Route to multiple paths based on value matchingConfiguration:
  • Select variable to switch on
  • Define multiple cases with values
  • Optionally set a default path
Outputs: One path per case, plus optional defaultExample use cases:
  • Route by customer segment (Enterprise, Mid-Market, SMB)
  • Handle different product tiers
  • Geographic routing
[SCREENSHOT: Switch node editor with multiple output paths] Caption: Route to different paths based on segment, tier, or other values
Purpose: Pause workflow execution for a specified durationConfiguration:
  • Duration amount (number)
  • Duration unit (minutes, hours, days)
Example use cases:
  • Wait before sending follow-up email
  • Give time for external processes
  • Stagger notifications
Delay nodes pause the entire workflow run. For time-based action scheduling within onboarding, use template action delays instead.

​
Human Task Nodes

Human task nodes pause the workflow and create items in the Queue Dashboard for team members to complete.
Purpose: Pause for a human to manually select and assign a CSMConfiguration:
  • Queue to route to
  • Instructions for the reviewer
  • Optional: Pre-filter CSM list
What the reviewer sees:
  • Account details and context
  • List of available CSMs
  • Selection interface
Output: Selected CSM ID flows to downstream nodes[SCREENSHOT: CSM Assignment task in queue dashboard] Caption: Team members see CSM assignment tasks in their queue
Purpose: Human reviews account and makes routing decisionConfiguration:
  • Queue to route to
  • Decision options (e.g., “Approve”, “Reject”, “Needs Review”)
  • Instructions and context to show reviewer
What the reviewer sees:
  • Full account context
  • CRM data snapshot
  • Decision buttons
Outputs: Multiple paths based on decision options[SCREENSHOT: Triage task showing account details and decision options] Caption: Reviewers see full context to make informed routing decisions
Purpose: Request approval from a specific person or roleConfiguration:
  • Title and description
  • Request from: Specific user OR role (admin, user)
  • Optional: Auto-approve after timeout
What the approver sees:
  • Approval request with context
  • Account details
  • Approve/Reject buttons with optional comment
Outputs: Two paths - “Approved” and “Rejected”[SCREENSHOT: Approval request in queue dashboard] Caption: Approvals show context and allow approve/reject with comments
Purpose: Wait for AE to complete handoff form with account contextConfiguration:
  • Select handoff template to use
  • Instructions for AE
What happens:
  • AE receives email with link
  • AE fills in answers (with AI suggestions)
  • AE assigns CSM
  • Workflow continues with collected data
Output: Handoff answers, assigned CSM[SCREENSHOT: Handoff form as seen by AE] Caption: AEs complete handoff forms with AI-assisted answer suggestions

​
Action Nodes

Action nodes execute automatically without human intervention.
Purpose: Automatically assign a CSM to the accountConfiguration:
  • Source: Variable (from upstream node) OR specific user OR round-robin
Example use cases:
  • Apply CSM selected in CSM Assignment node
  • Auto-assign to a specific CSM for a segment
  • Round-robin distribution
This node writes the assignment to the account. Use CSM Assignment (human task) to let someone choose, then Assign CSM to apply it.
Purpose: Choose which onboarding template to applyConfiguration:
  • Source: Specific template OR variable from upstream
Example use cases:
  • Apply different templates based on segment
  • Use template selected during triage
  • Default template for all accounts
[SCREENSHOT: Select Template node editor with template dropdown] Caption: Choose a template to apply to the account
Purpose: Send automated email during workflow executionConfiguration:
  • Recipients (to, cc, bcc) - can use variables
  • Subject line with variable support
  • Email body with rich text and variables
Variables available:
  • {{account.company_name}} - Company name
  • {{account.arr}} - Annual recurring revenue
  • {{csm.name}} - Assigned CSM name
  • {{csm.email}} - Assigned CSM email
  • Plus custom fields from CRM
[SCREENSHOT: Email node editor with variable picker] Caption: Compose emails with dynamic variables from account data
Use the variable picker (click ) to insert variables without typing. This prevents typos and shows available fields.
Purpose: Use AI to transform, classify, or analyze dataTransform types:
  • Classify - Categorize accounts (e.g., segment, risk level)
  • Extract - Pull specific information from text
  • Summarize - Create summaries of CRM notes
  • Score - Generate numeric scores based on criteria
Configuration:
  • Transform type
  • Input fields to analyze
  • Instructions for the AI
  • Output variable name
Example use cases:
  • Auto-classify accounts by segment based on CRM data
  • Extract key information from deal notes
  • Score account complexity for routing
[SCREENSHOT: AI Transform node editor showing classification setup] Caption: Configure AI to classify, extract, or transform data

​
Terminal Nodes

Purpose: Mark workflow completionConfiguration:
  • Label (e.g., “Success”, “Rejected”, “Needs Follow-up”)
Notes:
  • Workflows can have multiple End nodes for different outcomes
  • Each End node can have a different label for reporting
  • Reaching an End node marks the run as “completed”

​
Configuring Nodes

When you select a node, the properties panel opens on the right side. [SCREENSHOT: Properties panel showing node configuration options] Caption: The properties panel shows all configuration options for the selected node

​
Common Properties

  • Name - Display name for the node (shown on canvas)
  • Description - Optional notes about what this node does

​
Node-Specific Properties

Each node type has unique configuration options. See the node type reference above for details.

​
Using Variables

Many node properties support variables - dynamic values from earlier in the workflow:
  1. Click the button to open variable picker
  2. Select from available variables
  3. Variable is inserted at cursor position
Available variable sources:
  • Account data - Company name, ARR, domain, etc.
  • CRM snapshot - All fields from the triggering CRM record
  • Contacts - Contact list from CRM
  • Upstream nodes - Data output by previous nodes

​
Validating Workflows

Before activating, Thread validates your workflow:

​
Automatic Validation

Click “Validate” to check for issues:
  • ✅ All nodes are connected
  • ✅ Start node has valid trigger configuration
  • ✅ All paths lead to End nodes
  • ✅ Required node properties are filled
  • ✅ Variables reference existing data

​
Validation Errors

[SCREENSHOT: Validation dialog showing errors and warnings] Caption: The validation dialog shows all issues that need fixing
Error TypeMeaningFix
Disconnected nodeNode has no connectionsConnect or delete it
Missing configurationRequired field emptyFill in the property
Invalid variableVariable doesn’t existUpdate or remove reference
No path to endBranch doesn’t completeAdd End node or connection

​
Testing Workflows

Before activating, test your workflow with sample data.
1

Open Test Panel

Click “Test” button in the toolbar.
2

Configure Test Data

Either:
  • Select an existing account to use as test data
  • Create synthetic test data manually
[SCREENSHOT: Test panel with account selector and synthetic data builder] Caption: Test with real accounts or create synthetic test data
3

Run Test

Click “Run Test” to execute the workflow with test data.
4

Watch Execution

Nodes highlight as they execute. Human tasks pause until you complete them in the test interface.
5

Review Results

Check final state, data transformations, and any errors.
Test runs with real accounts don’t actually modify the account or send real emails. They simulate execution safely.

​
Saving and Activating

​
Save as Draft

Click “Save” to save changes without activating. Draft workflows don’t respond to CRM triggers.

​
Activate Workflow

1

Validate

Ensure validation passes with no errors.
2

Test

Run at least one successful test.
3

Click Activate

Click “Activate” in the toolbar.
4

Confirm

Review the trigger summary and confirm activation.
Active workflows immediately start responding to CRM events. Ensure your trigger conditions are correct to avoid processing unwanted records.

​
Best Practices

Start Simple

Begin with a linear workflow, then add branching as needed

Name Clearly

Use descriptive names that explain what each node does

Test Thoroughly

Test all paths before activating, including edge cases

Document Decisions

Use node descriptions to explain why branches exist

​
Common Patterns

Start → AI Transform (classify segment) → Switch (by segment)
  → Enterprise path → CSM Assignment → Assign CSM → Select Template → End
  → SMB path → Auto-assign → Select Template → End

Start → Condition (ARR > threshold)
  → Yes → Approval (manager)
    → Approved → Continue...
    → Rejected → End (rejected)
  → No → Continue without approval...

Start → Handoff Form (to AE) → Assign CSM (from handoff) → Select Template → Send Email (welcome) → End

​
What’s Next?

Running Workflows

Monitor execution and debug issues

Queue Dashboard

Process human tasks from workflows