n8n Automation Engineer — Ongoing Backend Owner for a Live Consciousness/Wellness Platform

Our program is a science-based consciousness training program delivered through Circle, with a substantial n8n automation backend connecting Circle, Supabase, OpenAI/Claude, Google Sheets, MailerLite, and Gmail. The system handles everything from new-member onboarding and level progression to an AI-driven chatbot and daily personalized member summaries. The original developer has limited availability and we need an experienced automation engineer to take command of this system going forward — maintaining what exists, fixing what's broken, and building new workflows as the platform grows. This is not a greenfield build. You'll be inheriting a live, production system with some gaps — a few dead code paths, some security cleanup needed, and a couple of silent failure modes we've already identified. We're being upfront about this because we want someone who's excited by that kind of work, not surprised by it three weeks in. What you'd own: Full responsibility for the 27-workflow n8n instance (self-hosted) — uptime, bug fixes, new workflow development Supabase schema and data layer supporting the automations Integration points with Circle's admin API, OpenAI/Claude API calls, Google Sheets, MailerLite, and Gmail Ongoing documentation as you go — we maintain a living technical worksheet and expect it to stay current Direct communication with the founder on priorities, with high autonomy to build and deploy once you're up to speed and trusted with production access What we need from you: Real n8n depth — comfortable reading and debugging complex existing workflows with nested Code nodes, HTTP requests, AI Agent nodes, and conditional branching, not just assembling templates from scratch Supabase experience — schema changes, RLS policies, writing/maintaining Postgres RPC functions API integration experience — comfortable working with REST APIs generally (Circle, OpenAI, Anthropic/Claude, Google Sheets, MailerLite are all in active use) Security-conscious habits — you should default to proper credential storage, least-privilege thinking, and flagging exposed data rather than needing to be told Clear written communication — you'll be documenting your own work for future continuity, and explaining technical tradeoffs to a non-technical founder Prior experience inheriting or auditing someone else's automation system is a strong plus.