Documentation
The kit isn't just files — it ships with the docs to get a non-developer from download to a working system in mock mode. This is a preview; the full guides are delivered with the kit.
Get from download to a workflow running in mock mode — typically about an hour.
End-to-end path: import workflows, connect the sheet, fill credential placeholders, run the acceptance test.
Excerpt
Step 1 — Import the four workflow JSON files into n8n. Step 2 — Create the Google Sheet from the template (tabs: Leads, OldLeads, ReactivationLog, ReviewRequestLog, WeeklyReports, ErrorLog). Step 3 — Keep MOCK_MODE on. No real messages send until you turn it off deliberately.
Importing each workflow, mapping nodes, and the webhook paths each one expects.
Excerpt
Workflow 01 listens on webhook `logivault-new-lead` and expects a JSON POST with name, phone, email, source, message, businessName, bookingLink, ownerEmail.
Exactly which credentials each workflow needs and where to paste them safely.
Excerpt
Credentials are referenced by placeholder only. Nothing real ships in the kit. You add your own keys in n8n's credential store — never in the workflow JSON.
Connect the AI, SMS, and email providers you and your client supply.
Adding an AI provider key and selecting a model for reply and report generation.
Excerpt
The kit is provider-agnostic for the AI step. Use OpenAI or Anthropic; the prompt files are written to work with either.
Provisioning a number, wiring credentials, and the mock-mode safety switch.
Excerpt
In mock mode, SMS nodes log to the sheet instead of sending. You flip to live only after the acceptance test passes.
Connecting an email sender and keeping deliverability sane from day one.
Excerpt
Use an authenticated sending domain. The sequences include required opt-out language — don't strip it.
Run it for a real client without creating problems for yourself.
The common failure modes (expired credentials, webhook 404s, sheet permissions) and fixes.
Excerpt
Most issues are credential or permission related. The ErrorLog tab is the first place to look; each row names the workflow and the failing step.
Consent before contact, opt-out in every message, honoring opt-outs, honest reviews.
Excerpt
Defaults are consent-first: opt-out language is built into every sequence, opt-outs are honored, and review requests are never gated or incentivized. Compliance in your jurisdiction is your responsibility.
A formal pass/fail test so you can prove the kit works before you sell it.
Excerpt
Run `node scripts/validate-json.js`, then work the acceptance test. Confirm leads log, consent is respected, and nothing sends in mock mode — then decide to go live.
Including a buyer acceptance test and a JSON validator so you can prove the system works the same day you download it.