Parallel Block

The Parallel block executes multiple workflow paths concurrently. Use it when you need to perform independent operations simultaneously -- like updating multiple systems, sending notifications to different channels, or processing data in parallel.

Configuration

How It Works

1. When the Parallel block executes, all connected downstream paths start simultaneously
2. Each branch runs independently with access to the same upstream data
3. When all branches complete, the Parallel block collects results and passes them downstream
4. If any branch fails, the error handling strategy determines the behavior

Example Patterns

Multi-System Update

Stripe (payment received) -> Parallel
    -> QuickBooks (record payment)
    -> Salesforce (update opportunity)
    -> Slack (notify #finance)
    -> Gmail (send receipt to customer)

Parallel Data Fetch

Start -> Parallel
    -> Stripe (get customer)
    -> QuickBooks (get invoices)
    -> Salesforce (get account)
-> Transform (combine all data) -> Agent (analyze)

Best Practices

• Use for independent operations. Parallel is most effective when branches do not depend on each other's results.
• Be mindful of API rate limits. Running many API calls in parallel can trigger rate limiting on external services.
• Keep branches balanced. A parallel block completes when its slowest branch finishes. One slow branch delays the entire block.