Workflow Editor

Email, name, custom text fields:

• Equals/Not equals - Exact match
• Contains/Does not contain - Partial text match
• Starts/ends with - Text position matching
• Is set/Not set - Check for value existence :::

  Created date, custom date fields:

• Before/After - Date range comparisons
• More/Less than - Relative time periods
• Is set/Not set - Check for date existence :::

  Custom number fields:

• Equals/Not equals - Exact number match
• Greater/Less than - Numeric comparisons
• Is set/Not set - Check for value existence ::: ::

Action Nodes

Action nodes modify subscriber data or group memberships when reached in the workflow.

Available Actions

Update Custom Fields: Modify subscriber information

• Set text field values
• Increment/decrement number fields
• Set date fields to specific values or relative dates

Group Management:

• Copy to groups: Add subscribers to additional groups
• Move to groups: Transfer subscribers between groups
• Remove from groups: Remove subscribers from specified groups

Subscription Management:

• Mark as unsubscribed: Immediately unsubscribe the subscriber

Webhook Nodes

Webhook nodes send data to external services when reached in the workflow, enabling integrations with CRMs, analytics platforms, and custom applications.

Configuration

Authentication

Webhooks include a Signature header containing an HMAC SHA-256 hash of your secret key. Verify requests on your server by hashing the same key and comparing signatures.

Available Field Tags

Use these placeholders in webhook URLs and body values:

Basic Fields:

• {{email}} - Subscriber email address
• {{name}} - Subscriber name
• {{created_at}} - When subscriber was added
• {{state}} - Subscriber status

Custom Fields: {{your_custom_field_tag}} for any custom fields you've created

Dynamic Data: Any custom data sent via API triggers or fetched via Data Fetch nodes

Data Fetch Nodes

Data Fetch nodes retrieve information from external APIs to use in subsequent email and webhook nodes.

Configuration

Response Format Requirements

API responses must be JSON objects with:

• String keys only
• String or number values
• Maximum 20 fields per response

Example response format:

{
    "user_id": "12345",
    "account_type": "premium",
    "last_login": "2024-01-15"
}

Authentication

Like webhooks, fetch requests include a Signature header with HMAC SHA-256 authentication.

Workflow Switch Nodes

Workflow Switch nodes transfer subscribers to different workflows, allowing you to create modular automation sequences.

Use Cases

• Common Entry Sequences: Start with a universal welcome flow, then branch to specialized nurture tracks
• Re-engagement Campaigns: Route inactive subscribers to different recovery workflows
• Segmentation Logic: Send different subscriber types through optimized sequences

Auto Layout

As workflows grow with multiple branches and conditions, nodes can overlap or become hard to follow. The Auto Layout button instantly reorganizes the entire workflow tree into a clean, balanced structure.

Click the Auto Layout button in the top-right toolbar to reorganize all nodes. The editor automatically zooms and pans to fit the entire workflow in view.

The layout engine:

• Centers the trigger at the top and arranges all child nodes below it
• Balances branches — condition nodes (yes/no paths) get equal horizontal space
• Spaces evenly — consistent vertical and horizontal gaps between all nodes
• Handles nesting — deeply branched workflows are laid out without overlaps

Generate with AI

You can generate an entire workflow structure from a plain-text description using AI. Instead of manually adding and connecting nodes one by one, describe what you want the workflow to do and AI builds the full node structure for you.

How to Use It

What Gets Generated

The AI creates the complete workflow structure including:

• Trigger configuration with the appropriate settings
• Email nodes with subject lines and preheader text (you design the email content separately using the email editor)
• Delay nodes with appropriate wait times
• Condition nodes with branching logic based on your description
• Action nodes for group management, field updates, or unsubscribes
• Webhook and fetch nodes when your description involves external integrations

After Generation

Once the AI generates your workflow:

1. Nodes are auto-laid out — the layout engine positions everything cleanly
2. Email content is not included — email nodes have subjects and preheaders, but you need to design the actual email content using the email editor on each node
3. Review the structure — check that the logic matches your intent, and adjust any nodes as needed
4. Activate when ready — test your emails and activate the workflow

Workflow Management

Validation and Activation

Before activating a workflow, ensure:

• A trigger is properly configured
• At least one action node exists
• All required fields are filled

Monitoring Performance

Track workflow performance through the built-in reporting:

• Completed: Successfully finished workflows
• Queued: Workflows waiting to execute
• Failed: Workflows that encountered errors

Testing Workflows

• Send test emails from the email node configuration
• Use test webhooks and API calls to verify integrations
• Manually trigger workflows with test subscribers

Best Practices