LoopfourBlocks
Parallel Block
Execute multiple workflow paths concurrently for faster processing
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
| Option | Type | Description |
|---|---|---|
branches | edges | Multiple output connections, each defining a parallel path |
waitForAll | boolean | Wait for all branches to complete before continuing (default: true) |
How It Works
- When the Parallel block executes, all connected downstream paths start simultaneously
- Each branch runs independently with access to the same upstream data
- When all branches complete, the Parallel block collects results and passes them downstream
- 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.
Loop Block
Iterate over collections sequentially
Condition Block
Branch based on conditions (one path only)
Frequently Asked Questions
A Condition block routes to one path based on a boolean expression -- either true or false, never both. A Parallel block executes ALL connected paths simultaneously. Use Condition for either/or decisions, Parallel for and/and operations.
By default, if one branch fails, the other branches continue executing. The Parallel block reports the failure after all branches complete. You can configure error handling to fail the entire workflow immediately if any branch fails.
There is no hard limit on the number of branches, but more branches mean more concurrent API calls and resource usage. Keep it reasonable -- 2 to 8 branches is typical.
Yes. You can nest a Parallel block inside a Loop to execute multiple operations concurrently for each iteration. This is useful for patterns like updating multiple systems for each item in a batch.