Multi-Step Workflow Design

Simple automations have a beginning, middle, and end. Complex automations look like trees — branching logic, parallel processing, loops, and sub-workflows. Without a clear architecture, these become unmaintainable within weeks. The most important principle: one workflow should do one thing well. Resist the temptation to build a single monolithic workflow that handles 12 different cases. Instead, build small, focused workflows that call each other. A 'New Customer' workflow might trigger a 'Send Welcome Email' workflow, a 'Create CRM Contact' workflow, and a 'Notify Sales Team' workflow — all running in parallel. Each sub-workflow is testable and replaceable independently. Use sub-workflows (n8n calls them 'Execute Workflow' nodes) to share logic across multiple automations. If 5 different workflows all need to look up a customer by email, extract that logic into a single 'Customer Lookup' workflow and call it from each. When the customer lookup logic changes, you update it in one place. Parallel processing is powerful but requires care. When you use n8n's Split In Batches node or execute multiple branches in parallel, the results need to be merged carefully. Data from parallel branches doesn't automatically interleave — you need to explicitly merge it with the Merge node. Think about how your parallel paths will reunite. For long-running workflows (those that take minutes or hours), design with checkpoints. After each significant step, write the current state to a database. If the workflow fails partway through, it can resume from the last checkpoint rather than starting over.

Let's build a real example: a sales pipeline workflow that runs when a new deal is created in your CRM. The trigger: new deal created in Pipedrive (webhook). Branch 1 (parallel): Enrich the contact. Call Clearbit's API to get company size, industry, and LinkedIn. Update the deal with this enrichment data. Branch 2 (parallel): Create supporting assets. Generate a personalized proposal template using the deal value and industry. Store it in Google Drive. Add the Drive link to the CRM deal. Branch 3 (parallel): Notify the team. Post to the #new-deals Slack channel with deal details. If deal value > $10k, also send a direct Slack message to the founder. Merge: After all three branches complete, run a final step that creates a follow-up task in the CRM for 2 days from now. This workflow accomplishes in 15 seconds what used to take 30 minutes of manual work. The parallel branches mean all three things happen simultaneously — total wall time is whatever the slowest branch takes, not the sum of all three. When building this, draw it out first. Literally sketch the branches on paper before touching n8n. The 5 minutes of planning saves 30 minutes of re-wiring.