Complex workflows
Multi-branch logic, loops, merges, and sub-workflows — the orchestration Zapier’s linear model can’t express cleanly.
Complex multi-branch workflows, custom and code nodes, self-hosting, error workflows, and the automation Zapier gets too expensive for. 3+ years — n8n is my default for production builds. Same productized pricing: USD, fixed, no surprises.
The work that gets billed — not a marketing list. If your gap is here, we can talk concretely.
Multi-branch logic, loops, merges, and sub-workflows — the orchestration Zapier’s linear model can’t express cleanly.
Deploy and harden n8n on your own infra (Docker, queue mode, env + secrets) so tasks are effectively free and data stays yours.
Function and Code nodes in JS/Python for anything the standard nodes can’t — transforms, custom API calls, signing.
Build a custom node when an integration deserves a first-class, reusable block instead of a code step.
Dedicated error workflows, retries, and alerting so failures are caught, logged, and surfaced — not lost.
OpenAI / Anthropic / agent nodes wired into the flow for classification, extraction, and tool-calling.
Webhook triggers, polling, and raw HTTP for any REST/GraphQL API — with auth and pagination handled.
Move heavy Zapier workflows to n8n to cut task costs, with parity and a clean cutover. Documented, with a Loom.
Spark, Audit, Sprint, or Build — same productized cadence as every track. USD pricing, fixed, no surprises. Bigger or ongoing needs sit one section down.
One workflow built and shipped — or one failing workflow fixed properly. The smallest way in.
Read-only review of your n8n instance (or your case for one) with a 30-day roadmap.
Two to three production workflows shipped end-to-end — the workhorse engagement.
One bigger build — a self-host rollout, a custom node, or a migration off Zapier.
Several builds wired into one operation → the Stack bundle. Ongoing help → Automation Care, three tiers from $750/mo. Both are cross-stack and scoped on the main packages page.
The ones that actually come up on intro calls.
Depends on volume and data sensitivity. High volume or data you want to keep on your own infra → self-host (tasks effectively free). Low volume / no ops appetite → Cloud. The audit gives you a clear recommendation.
Cost at volume (self-hosted tasks are effectively free), real branching/loops/sub-workflows, code nodes, and data control. For low-volume simple automations Zapier is often fine — I’ll tell you honestly which fits.
Yes. When an integration is used a lot, a custom node beats repeated code steps — reusable, typed, and easier for your team to maintain.
Yes — OpenAI/Anthropic and agent nodes for classification, extraction, drafting, and tool-calling, with the same error handling as the rest of the flow.
It’s my default for production builds, 3+ years. The $499 audit is the cheapest test, and I’m happy to screen-share real workflows for 20 minutes first.
The fastest path to a yes-or-no is a 5-minute brief. If it doesn't fit the standard packages, say so — most don't, and most get scoped anyway.