Johnny n8n Playbook (Onboarding + Implementation Plan)

For: James Jestes (AgentsOPS / FreshFlip / Daytona real estate) Date: 2026-02-05 Status: DRAFT v0 (approve/adjust before build)

0) Outcome (what “good” looks like)

Within 2–4 weeks, James has a repeatable automation operating system that: - Captures leads from AgentsOPS + FreshFlip funnels without duplicates. - Delivers lead magnets instantly and runs smart follow-ups (email + optional SMS/WhatsApp). - Runs a human-in-the-loop content engine (idea → draft → approval → publish → repurpose). - Runs a listing marketing + follow-up pipeline (new listing → assets → copy → posts → tasks → follow-up). - Has a single “Ops console”: errors, retries, audit logs, and dashboards.

1) How we’ll use n8n (the architecture)

1.1 Environments

• DEV (safe playground): new workflows + credential testing.
• PROD (reliable): only approved workflows; strict error reporting.

Minimum viable: start with one instance but enforce naming + folders to simulate dev/prod separation.

1.2 Source of truth (pick 1–2, keep it simple)

Recommended (practical for James): - Postgres (n8n internal DB) for workflow runtime state. - Supabase for FreshFlip (already in motion; beta_signups table exists). - Google Sheets OR Airtable OR Notion as the “Ops/CRM-lite” until a full CRM is unified.

Rule: one canonical Lead ID (email normalized → lower(email)), and every workflow must be idempotent.

1.3 Integration categories

• Lead Capture: web forms, FB group lead magnets, landing pages, link in bio.
• Lead Nurture: email sequences, calendar scheduling, reminders.
• Content Engine: research → outline → draft → approvals → publish.
• Real Estate Ops: listings, showing feedback, open house follow-up, investor outreach.

1.4 “Ops” workflows (non-negotiable)

These prevent n8n becoming a fragile spaghetti mess. - Global Error Workflow (n8n setting): catches failures, alerts James, logs payload + run URL. - Retry + dead-letter pattern: retry transient failures; dead-letter the rest into a table/sheet for manual fix. - Audit log table (lightweight): workflow_name, run_id, event_type, lead_id, status, error, timestamp.

2) Onboarding plan (implementation sequence)

Phase A — Discovery + mapping (2–3 hours)

Deliverable: a single “Automation Map” (systems + triggers + outputs). - Current lead sources (AgentsOPS): - Website forms (which builder?) - Facebook group entry + posts + DMs - Calendly (if used) - Email list provider (ConvertKit/Mailchimp/etc) - FreshFlip lead sources: - Lead magnet landing page (“Free Turnover System”) - Beta signup flow (beta_signups) - Current content ops: - Where ideas live (Notes/Notion/Sheets) - Where publishing happens (FB group, IG, YT, email) - Listing ops: - Where listings are tracked (CRM/MLS export/Google Sheet)

Decision points to confirm: 1) Primary CRM destination for all leads (HubSpot? Follow Up Boss? Airtable? Sheets?). 2) Primary email sender (Gmail vs SendGrid/Mailgun). 3) SMS/WhatsApp provider (Twilio vs OpenClaw WhatsApp channel vs later).

Phase B — Foundation setup (half day)

• n8n deployed (see install plan).
• Credentials added:
  • Google (Drive, Sheets, Gmail)
  • Supabase (FreshFlip)
  • OpenAI/Claude (content + classification)
  • Slack/Discord (alerts + approvals) OR email-based approvals
• Shared conventions:
  • Workflow naming: FF - Lead Magnet - Delivery v1, AOPS - Content - Weekly Batch v1
  • Foldering: /FreshFlip, /AgentsOPS, /Listings, /Ops
  • Variables: use env vars for base URLs, API keys, template links.

Phase C — Quick wins (days 1–3)

1. FreshFlip lead magnet autopilot (capture → deliver → follow-up)
2. Agent attraction lead routing (capture → tag → notify → task)
3. Content engine: idea → draft → approval queue (no publishing yet)

Phase D — Scale + harden (week 2)

• Add segmentation, scoring, and richer reporting.
• Add “at-risk / SLA reminders” (FreshFlip operations once app emits events).
• Add listing automation pack.

3) Operating principles (keep workflows stable)

3.1 Idempotency by design

Every lead ingestion must: - Normalize email_lower. - Upsert instead of insert. - Store a source_event_id (form submission id, webhook request id, etc.).

3.2 Human-in-the-loop for anything public

For content + outbound messages: - Draft → approval step → publish. - Store approved copy + timestamp + approver.

3.3 Prefer “one workflow per business outcome”

Avoid mega-workflows. Use: - Parent orchestrator workflow - Sub-workflows (“Execute Workflow” node) for reusable actions: - UTIL - Upsert Lead - UTIL - Send Delivery Email - UTIL - Log Audit Event

3.4 Error handling standard

• Use Error Trigger workflow + Slack/email alert.
• In each workflow:
  • Wrap external API calls with retry (HTTP 429/5xx).
  • Branch on “expected errors” (duplicate lead, missing field).

4) Julian Goldie n8n pattern scan (what to emulate)

Note: I could not fetch full video watch pages (YouTube returned “Sign in to confirm you’re not a bot”). I was able to parse his channel search results for “n8n” and extract titles + formats.

Observed patterns from his n8n catalog: - Hook-driven titles: “INSANE”, “DESTROYS”, “NEW”, “FREE template”, “in 51 seconds”, “1 click”. - Two-track content strategy: - Shorts: fast results (0:19–0:59) → curiosity + template CTA. - Long form: “FULL COURSE” (1h / 5h / 8h) → depth + trust. - Angle: n8n as the practical “AI agent builder” (Claude + agents + MCP + workflow builders + scrapers). - Offer packaging: explicit “FREE template” frequently in titles.

Examples (titles pulled from channel search for n8n): - “How to Build AI Agents in 51 Seconds using N8N” (short; very high views) - “N8N FULL COURSE 5 HOURS (Build & Automate Anything)” (long-form course) - “This N8N Automation Templates Is INSANE (FREE!)” (template hook) - “Claude: Build ANY n8n AI Agent in 1 Click!” (agent + 1-click promise) - “NEW N8N Scraper Agent (FREE!)” (scraping angle) - “NEW n8n 2.0 Update Is INSANE!” (release/news angle)

Operating principles to steal for AgentsOPS/FreshFlip: - Lead with outcome (not nodes). - Provide templates and make setup “copy → paste keys → run”. - Teach via build-along plus a real business use case. - Always include a CTA: template download → email capture → nurture → consultation.

What to validate later (when YouTube access is available): - His exact template distribution method (GitHub? Gumroad? n8n marketplace?) - His recommended stack (self-host vs cloud, DB choices) - His exact AI prompt + memory patterns inside n8n

5) The initial automation backlog (James-specific)

FreshFlip (highest leverage)

• Lead magnet delivery + follow-up (segmented by # units and market).
• Beta signup notifications + enrichment.
• (Later) Ops alerts: checkout → RED → at-risk → cleaner nudge.

AgentsOPS

• Agent attraction lead capture from funnel(s) + Facebook group.
• “AI audit” intake form → auto-create Notion/CRM record → schedule call.
• Weekly content batch: 5 hooks, 5 posts, 1 email newsletter draft.

Listings

• New listing → Drive folder + naming standard + asset request.
• Listing copy pack (MLS description + social captions + email).
• Open house follow-up (attendees → tags → SMS/email sequence).

6) Next questions for James (answer these to finalize)

1. What is the current form stack for AgentsOPS + FreshFlip (Webflow, Carrd, WordPress, GoHighLevel, etc.)?
2. Where do leads live today (CRM name), and what fields are mandatory?
3. Preferred outbound email sender: Gmail or a dedicated sender (SendGrid/Mailgun)?
4. Do we want SMS/WhatsApp in week 1, or email-only until copy is dialed?
5. Where should content calendar live (Notion vs Google Sheet)?