email-lead-gen

name	email-lead-gen
version	1.0.1
description	OpenClaw Email Lead Generation — the complete outreach and pipeline system for your agent. Guided setup builds your config, Template Forge creates custom email sequences from a voice interview, and 3-tier architecture scales from manual pipeline tracking to fully automated cron-driven outreach. Add leads, score them, run email sequences, monitor replies, get morning briefings, and track your entire funnel — all through conversation. v1.0.1: timezone support, per-domain rate limits, email warmup, compliance/unsubscribe, audit logging, inbound HTML stripping, credential security, temp-file email body (fixes JSON escaping). Works standalone or alongside AI Persona OS. Built by Jeff J Hunter.
tags	["leadgen","email","outreach","pipeline","crm","sales","leads","sequences","cron","automation","follow-up","prospecting"]
author	Jeff J Hunter
homepage	https://jeffjhunter.com
metadata	{"openclaw":{"emoji":"🎯","requires":{"bins":["bash","sed","find","grep","date","wc"],"optionalBins":["openclaw","jq"],"env":[],"optionalEnv":["SMTP_HOST","SMTP_PORT","SMTP_USER","SMTP_PASS","GMAIL_APP_PASSWORD"]},"stateDirs":["~/workspace/leadgen","~/workspace/leadgen/leads/active","~/workspace/leadgen/leads/archive","~/workspace/leadgen/templates","~/workspace/leadgen/sequences","~/workspace/leadgen/campaigns","~/workspace/leadgen/reports/daily","~/workspace/leadgen/reports/weekly"],"persistence":"Lead data stored as JSON files under ~/workspace/leadgen/. All file operations routed through assets/leadgen-helper.sh which enforces input sanitization, path validation, and JSON validation in code. Templates and sequences are JSON. Config is YAML. Reports are markdown. No database required. No network activity during setup — email integration is opt-in Tier 2+.","cliUsage":"The openclaw CLI is OPTIONAL. Core pipeline tracking (Tier 1) works entirely with standard Unix tools and the bundled helper script. The openclaw CLI is only used for: 1) 'openclaw cron add' for automated sequences (Tier 3), 2) browser-based Gmail access (Tier 2 option). The agent checks for the openclaw CLI before attempting these commands."}}

🎯 OpenClaw Email Lead Generation

The complete outreach and pipeline system for your OpenClaw agent.

Add leads. Build custom email sequences with a guided interview. Score prospects. Run automated follow-ups. Get morning pipeline briefings. Track your entire funnel from first email to closed deal — all through conversation.

---

⛔ AGENT RULES — READ BEFORE DOING ANYTHING

1. Use EXACT text from this file. Do not paraphrase menus, stage names, or instructions. Copy them verbatim.
2. NEVER tell the user to open a terminal or run commands. You have the exec tool. USE IT. Run every command yourself via exec. Before each exec, briefly explain what the command does so the user can make an informed decision on the Approve popup.
3. One step at a time. Run one exec, show the result, explain it, then proceed.
4. NEVER overwrite existing leadgen files without asking. If ~/workspace/leadgen/ exists, ask before overwriting anything.
5. NEVER send an email without explicit user approval. Draft first, show the draft, wait for "send it" or "looks good." The ONLY exception is if the user has explicitly enabled auto-send with a grace period in config.
6. Scope: ~/workspace/leadgen/ only. All file operations stay under this directory. Never create files outside without explicit approval.
7. Cron jobs are opt-in (Tier 3). Never schedule recurring tasks unless the user explicitly requests it and completes Tier 3 setup.
8. Lead data is confidential. Never expose lead email addresses, names, or company details in shared channels. Pipeline summaries in shared channels use anonymized data ("Lead #47" not "John at TechCo").
9. Rate limits are sacred. Never exceed the configured daily/hourly email limits. If the queue exceeds limits, defer to the next send window and inform the user.
10. Template Forge is a guided flow. When the user wants to create templates, follow the interview process in references/template-forge.md. Don't dump all questions at once.
11. USE THE HELPER SCRIPT FOR ALL FILE OPERATIONS. Never construct raw shell commands with user input. Always route through assets/leadgen-helper.sh which enforces path validation, input sanitization, and JSON validation in code — not in prompts. See Helper Script Reference below.

---

🛡️ Helper Script — Security Layer

All file operations go through assets/leadgen-helper.sh. This script enforces sanitization in , not in prompt instructions. The agent must NEVER bypass it to write lead files, templates, sequences, or config directly.