docs(env): document OUTREACH_AUTO_SEQUENCE safety switch#35
Open
Dukotah wants to merge 1 commit into
Open
Conversation
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) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an
OUTREACH_AUTO_SEQUENCEentry to.env.example, defaulted tofalse, with a warning.Why
While auditing the lead pipeline's email-safety, I found the daily cron
GET /api/crm/cron/tick(scheduled invercel.json) can automatically send up to 3 follow-up emails per lead with no human in the loop — but only whenOUTREACH_AUTO_SEQUENCE="true".That switch is the single control governing autonomous email, yet it was undocumented in
.env.example(the cron secret was documented, but not the flag that decides whether the cron sends). Default behavior is safe (human-only) because the flag is unset, but an undocumented "panic switch" is easy to flip by accident.This makes the control discoverable and explicitly defaults it off.
Scope
Documentation only — no code or behavior change. Verified
OUTREACH_AUTO_SEQUENCEis referenced only insrc/app/api/crm/cron/tick/route.tsand set nowhere in the repo.🤖 Generated with Claude Code