From 637e5996d527ce71496a490e3ca57a6e34ccb74d Mon Sep 17 00:00:00 2001 From: Dukotah Date: Thu, 25 Jun 2026 10:50:31 -0700 Subject: [PATCH] docs(env): document OUTREACH_AUTO_SEQUENCE safety switch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The daily cron at /api/crm/cron/tick can automatically send up to 3 follow-up emails per lead, but ONLY when OUTREACH_AUTO_SEQUENCE="true". That switch was undocumented in .env.example — the cron secret was documented, but not the flag that actually governs autonomous sending. This adds the entry, defaulted to false, with a clear warning that enabling it makes outreach non-human. Documentation only. No code or behavior change. Co-Authored-By: Claude Opus 4.8 (1M context) --- .env.example | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.env.example b/.env.example index f8d07ea..3b801ad 100644 --- a/.env.example +++ b/.env.example @@ -47,6 +47,16 @@ RESEND_WEBHOOK_SECRET= # Any long random string; in production the x-vercel-cron header is also accepted. CRON_SECRET= +# ⚠ SAFETY SWITCH — automatic outreach email. LEAVE UNSET (or "false"). +# By default the cron does NOTHING: a due follow-up stays in "Due today" until a +# human sends it from the gated composer — outreach email is human-only. +# Setting this to "true" makes /api/crm/cron/tick AUTOMATICALLY SEND up to 3 +# follow-up emails per lead with no human in the loop (it still honors the +# suppression list, OUTREACH_DAILY_CAP, and OUTREACH_DOMAIN_VERIFIED, but those +# are the ONLY remaining gates). Do not enable unless you explicitly want +# autonomous sending. See src/app/api/crm/cron/tick/route.ts. +OUTREACH_AUTO_SEQUENCE=false + # ── Optional: extra integrations ───────────────────────────────────────────── # Google PageSpeed Insights key — raises the rate limit on website audits.