Automation posts from Will's Journal.
These are the Automation posts from Will's Journal — writing from this practice, not the Automation service page.
The Automation practice: The work that should not need you.
Which Automation posts are in this archive?
Automation After the show is not you at 1 a.m.
Post-show onboarding — thank-you, join path, merch nudge — belongs in a human-gated n8n rail, not your thumb at load-out.
Automation Paperwork that is not the plant
Invoice and PO matching, intake, and support triage in n8n with Metrc fences — the paperwork operators hate, not a menu widget.
Automation Saturday still books — the missed-call rail for trades
A missed-call text-back that routes zip and books a slot beats voicemail and Saturday desk coverage you cannot keep staffed. If a kid is cheaper, say so.
Automation Why doesn’t worker concurrency cap my n8n sub-workflows
Worker concurrency does not cap n8n sub-workflows. Each Execute Workflow child is a new execution the production limit skips, usually on the parent worker.
Automation When does Continue on Fail hide real API errors in n8n
Continue on Fail hides real API errors when the node fails but the run stays green. Error Workflow never fires; last-valid data often walks into the next write.
Automation Why is one giant n8n canvas a production liability
One giant n8n canvas is a production liability because debug, credentials, retries, and deploys share one blast radius. Split it with named contracts.
Automation The First Automation a Small Business Should Ship
Ship intake and onboarding first: form to CRM, confirmation, one nudge. DIY reversible writes; buy the $500 Automation Audit when a first bot can spam clients.
Automation Multi-Client n8n for Agencies: Isolate Credentials or Inherit Incidents
Agencies isolate n8n by instance or paid Projects — folders are not tenancy, and hosting client credentials needs a verified license check with n8n first.
Automation Production n8n: The Handbook for Automations That Survive Contact With Reality
Run n8n in production with idempotency keys, dead-letter queues, verified webhooks, credential lifecycle, and queue mode only when concurrency hurts you.
Automation How do agencies onboard multiple clients for Google OAuth on a self-hosted n8n instance
Onboard each client with their GCP project, n8n's exact OAuth callback, one Google credential, and a scripted walkthrough of the unverified-app warning.
Automation How does n8n refresh OAuth access tokens
n8n stores refresh tokens in encrypted oauthTokenData and refreshes generic OAuth2 on 401. Google needs access_type=offline before a refresh token exists.
Automation Who Owns the Automation When the Builder Leaves
When the builder leaves, automations survive only if a named owner, a half-page runbook, and company-owned credential handoff are already in place now.
What should I know about this Automation archive?
- What is this Automation archive?
- These are the Automation posts from Will's Journal — writing from this practice, not the Automation service page.
- Is this the Automation service page?
- No. This is a journal lane archive. The Automation practice is at /automation. The work that should not need you.