Workflow pack
Four n8n automations for a local business that prepare drafts for you to check and send yourself: a site health check, a lead-form reply, a missed-call text-back and a review request, with a guide that explains every node.
Free lesson on this topic: Self Host n8n with Docker for Beginners (Free, Step by Step) (opens YouTube)
Local Business Automation Pack
$29 one-time
After Stripe checkout you land on your own access page with every file. Each download link works for 7 days; open the page again for fresh links. Lost it? Recover it with your Stripe receipt.
One zip: a PDF guide plus four n8n workflow files, a README and a Docker compose file
This title: $29, paid once. No subscription.
Nothing else from ATLAS Academy: no subscription, no renewal, no add-ons. If a tool under You need has paid plans, that company sets the price.
Checkout ends on your own access page with every file. Each download link works for 7 days; open the access page again for fresh ones.
Lost the page? Recover it with the email your Stripe receipt went to and the receipt number on it.
Sneak peek
Cut from the files you get after checkout. Nothing here is a mock-up.
Pages 1, 2, 3 and 5 of 29, exactly as they print. Select a page to see it full size.
Every file in the zip, 7 in all.
# Local Business Automation Pack: the four workflows
Last verified: 1 Oct 2026
Four n8n workflow files you can import, each matching a chapter of the guide. They draft; they never send.Contents
Counted from the files on 1 Oct 2026.
| Format | One zip: a PDF guide plus four n8n workflow files, a README and a Docker compose file |
|---|---|
| Guide | 29 pages, US Letter, 10 chapters and an appendix |
| Workflows | 4 importable n8n files, 9 nodes each, saved unpublished, no credentials inside |
| Tested on | n8n 2.40.7, self-hosted with Docker, 1 Oct 2026 |
| You need | A computer that can run Docker, about an hour, no programming |
How it works
Buy opens Stripe's secure checkout. We never see your card details.
You land on it right after checkout, with every file.
First up: Start here (The guide).
Each download link works for 7 days. Open the page again for fresh links.
What you will finish
Four n8n workflows on your own computer: each new lead, missed call or finished job gets a drafted reply in a plain text file for you to read and send yourself, and your website is checked every 15 minutes and logged as OK, DOWN or UNKNOWN.
The tested lead-form run from Chapter 4: a made-up lead (Dana Reyes, dana@example.com, "Need a quote for a kitchen faucet repair") comes back as {"status":"draft","sent":false,...} with the drafted email, and one new row in inbox/Leads.md.
A written guide and four importable n8n workflow files, by Miro. Each workflow checks its input, writes the lead, call, job or site status to a plain text file on your own machine, and drafts the reply for you to send. Nothing is sent by the files, and nothing needs an account, a key or a password. Import them in an afternoon, test them with made-up data, and keep the owner in the loop.
Every file the purchase delivers, as listed on your access page.
Local Business Automation Pack (zip: PDF guide, 4 n8n workflows, README, docker-compose)
Beyond the free material
Exactly what you get
Human review is the method
A made-up lead from the contact form: Dana Reyes, dana@example.com, +1 (555) 010-2233, "Need a quote for a kitchen faucet repair".
Subject: Thanks for getting in touch with [Business name]. Hi Dana, thanks for reaching out to [Business name]. We got your message about "Need a quote for a kitchen faucet repair" and will get back to you within one business day.
The workflow answers {"status":"draft","sent":false,...,"next":"owner approves before anything is sent"} and adds a row to inbox/Leads.md. No workflow in the pack has a sending step.
You read the draft, change it if needed, and send it from your own email.
Nothing is sent. The draft stays in Leads.md.
What this control doesn't do. The gate is the missing send step: nothing makes you read the file, and "within one business day" is yours to change to what you can keep. Chapter 9 explains adding a send step later, and why last.
If you get stuck
A call to the Production URL of a workflow that isn't published, or to a Test URL when the canvas isn't listening404: the webhook is not registeredFor a test, select Execute workflow, then send one call per click. For production, publish the workflow; if you published from the command line, run docker compose restart.
An edit to the draft text with a quote mark inside it500 on every call; n8n underlines the problem in Validate & draftWrite we\'re, or "we are", inside the draft.
Check in order: the run succeeded in Executions; the compose file still has ./inbox:/inbox and N8N_RESTRICT_FILE_ACCESS_TO=/inbox; the inbox folder exists and your user can write to it (on Linux, sudo chown 1000:1000 inbox).
A file path changed in the workflow but not in the compose fileA permission error on Append to fileThe file fence is doing its job. Keep the workflow's /inbox/... path inside N8N_RESTRICT_FILE_ACCESS_TO, and change both together.
And 4 more like these.
Tested with
Imported with no errors and exported back identically. The site check ran with five cases (OK, OK with expected text, two DOWN, UNKNOWN). The three webhook workflows answered good input with a draft and sent: false, bad input with a 400 and no row, and a deliberately malicious test lead was escaped.
Recorded in the pack's verify log
Curriculum
Each lesson, note or file, in the order you'll meet it.
The same rules, draft before send and unknown is never OK, taken further: an agent that picks actions from a closed list and asks before it acts.
Something else? Write to Miro.
No. Every workflow writes a draft to a file and answers sent: false. There is no sending node in any file. Chapter 9 explains how to add one later, and why to add it last.
No. The pack runs on n8n's free self-hosted edition with Docker, on your own computer or server. n8n's licence allows using it for your own business and for automation services you offer to clients.
No. Every change is editing a short list or a placeholder such as [Business name] inside a box. The code in the workflows is already written and explained node by node.
It works with anything that can send a web request (a webhook) to a URL, which most form tools and business phone systems can. If yours can't, you can still add a row with one command and get the draft; the guide shows how.
They were imported, run and exported again on n8n 2.40.7 on 1 Oct 2026. The appendix lists exactly what was sent and what came back, including a deliberately malicious lead that was escaped correctly.
A zip with a PDF (US Letter) and a workflows folder of n8n JSON files, a README and a docker-compose.yml.
14-day money-back guarantee: if it isn't useful, email us within 14 days of purchase for a full refund, no questions asked. Refund policy
One purchase covers one business: the buyer and the people who work in that business may use the guide and the workflow files, including on the n8n they run for it. Please don't resell or share the files publicly. The buyer must be an adult.
Help
Miro replies by email within 2 business days.