01 / Where n8n fits
A good fit for workflows with branching logic.
n8n suits workflows that need conditional logic or custom code, or that handle data you would rather not route through a third party's servers. For a simple two step connection, Make or Zapier is often enough, and I'll tell you which you need before I build anything. I compare the three in more detail on sethforte.com.
02 / What I build
Workflows for the work that repeats.
Lead handling and routing
New inquiries are captured and assigned, then answered on a schedule you set.
Billing and collections
Invoices and payment reminders move on their own, with a record of what was sent.
Reporting
Scheduled pulls from your systems into the report you already read.
Internal approvals
Requests reach the right person and wait for a decision without chasing.
03 / Keeping it running
A workflow can run green and still do nothing.
The failure I see most is an automation that reports success while the work never happened. I add checks that confirm the outcome and alerts that reach a person when it didn't. I wrote about that in catching failures nobody notices.
04 / Example
A build I can point to.
- For a marketing operations team I built a set of 22 n8n workflows that cover their day to day.
05 / How I work
Remote, from Grapevine.
I'm based in Grapevine, Texas, and I work with companies across Dallas-Fort Worth and the rest of the US by video call and shared screens. I don't visit client offices. When the build is done you own the accounts and the code, and I hand over the documentation.
06 / Questions
Before you book.
Cloud or self hosted?
Either. I'll recommend one based on where your data should live and who will maintain it.
Do you build on Make or Zapier too?
Yes, when they fit better. I'd rather match the tool to the workflow.
Where does a project start?
With a Growth Systems Audit, a written diagnostic of your workflows and what each fix would take.
07 / Next step