Lessons from n8n, Make.com, API connections, webhooks, lead routing, cron jobs.
Set up an automated cron job to back up work to GitHub every 15 minutes
Created a cron job that ran git commit daily
The cron was committing changes but NOT pushing them to GitHub. The commits sat locally with no remote backup. Assumed "git commit" included "git push" — it does not.
Updated the cron script to include git push backup main explicitly after the commit.
Yes — "Cron for Dummies: Why Your Automated Backups Aren't Actually Backing Up"
Run multiple AI agents (James-ops, James-research) working on the same repo simultaneously
Both agents used the same default git identity
Couldn't tell which agent made which commit. When one agent broke something and the other tried to fix it, the commit logs were useless for attribution.
git log --format="%an <%ae> - %s" to verify attributionNo — multi-agent ops lesson
Have James-ops fix issues independently after James-research had already resolved them
Both agents had their own memory and context
James-ops still showed Cloudflare 503 errors from April 14 — errors that James-research had already fixed. The ops agent had stale context and wanted to re-fix a solved problem.
Added "CURRENT SYSTEM STATUS" section to MEMORY-PRIMER.md. Both agents must read this section FIRST on startup. Lists what's working, what's not, known issues. Any agent can update it when status changes.
No — multi-agent coordination lesson
Connect website contact forms to Make.com to automate lead notifications
Set up a Make.com webhook endpoint, tried to POST form data to it
Make.com's webhook needs to be "activated" with an action after receiving data, or it times out. The webhook appeared configured but silently failed.
Used Formspree → Make.com webhook path (requires Formspree Pro subscription). Or kept manual form handling as fallback.
Yes — "Webhook Woes: Why Your Forms Aren't Sending (And Make.com's Dirty Secret)"
Access n8n via API from a cloud agent to create and manage workflows
Used standard Bearer token authentication header
Got "X-N8N-API-KEY header required" error. n8n uses a custom header, not the standard Bearer token format.
Created workflow JSON files for Scott to import manually into n8n. The cloud agent couldn't access n8n directly.
X-N8N-API-KEY header, not Authorization: BearerYes — "n8n for Non-Developers: How to Actually Get Your Workflows Working"
Decide whether to use multiple Make.com accounts for different automations
Considered having separate accounts for client work vs internal automation
Scott said: "No, keep it simple — one account with multiple scenarios." The proposed complexity was unnecessary.
One Make.com account, multiple scenarios, clean naming convention.
No — general process principle
Have the cloud-based AI agent directly send emails, access n8n, and interact with local services
The agent tried to call localhost services, SSH into servers, and use local-only APIs
"AI on cloud can't access local servers — need explicit API keys" — The agent is cloud-based, with no direct access to local infrastructure (n8n, Make.com, file server, etc.)
Yes — "The Cloud Agent Trap: What AI Can and Can't Do On Your Infrastructure"
Create a reusable quality gate that catches static site failures before deployment, preventing the pattern where sites are declared "deploy-ready" but have missing DOCTYPE, broken forms, or no tracking.
Manually checked each page with grep for DOCTYPE, Formspree forms, GA4 tracking, SEO meta, sitemap, robots, CSS. This worked once but was not repeatable.
The landscape-greensboro.com site had been declared "deploy-ready" twice without a formal validation step. Both times, critical issues were found only after investigation — missing DOCTYPE, WordPress shortcodes, no GA4, no meta descriptions, broken CSS pipeline.
Created automation/validate-static-site.py — a standalone Python script that:
Yes — "The Pre-Deploy Checklist: How to Never Ship a Broken Website Again"