The email-worker is an ancillary input plugin that allows you to trigger automated trades via raw email alerts. While webhooks are the standard path, many legacy systems, charting platforms, or custom newsletters only distribute trade signals via email.
This tutorial walks you through setting up email-worker credentials, configuring regex subject scanning patterns, and securely routing messages.
🛜 1. Injecting Email Connection Credentials
To allow email-worker to log into your dedicated signals inbox, inject your SMTP/IMAP mailbox credentials as encrypted Workers Secrets:
Always use a dedicated email address solely for trade signals. Never use
your personal inbox. Additionally, configure your email provider (e.g., Gmail,
Fastmail) to require an App Password rather than your master account
credentials to ensure tight access control.
🔎 2. Configuring Regex Parsing Rules in KV
Once email-worker establishes connection, it scans the inbox on a background schedule, evaluating incoming subjects and message bodies against Regular Expression (regex) patterns defined in CONFIG_KV:
The Parsing Mechanism
When an email is scanned:
- The worker matches the subject. If the subject is
"TRADE SIGNAL: Breakout Detected", the check passes.
- The worker scans the email body using the regex patterns:
- Body:
"...we are entering a LONG position on SOL/USDT..."
- Hitting
email:coin_pattern resolves: SOL
- Hitting
email:action_pattern resolves: LONG (translated internally to BUY).
- Automatically triggers an order via the
trade-worker service binding.
🛡️ 3. Security Audits: SPF & DKIM Validation
To prevent malicious “spoofing” (e.g., an unauthorized sender trying to forge a trade signal to your inbox):
- Sender Validation: The
email-worker parses the email’s headers and matches the sender’s address against a safe allowlist in KV: email:authorized_senders = ["alerts@tradingview.com"].
- DNS Verification: The worker validates the SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) headers to verify that the message physically originated from the authorized domain and was not intercepted.
🧪 4. Testing Your Email Pipeline
To verify that the email signal ingestion loop works perfectly:
- Compose a mock email from your authorized sender address.
- Subject:
TRADE SIGNAL: Cross Over
- Body:
Action: SHORT, Symbol: ETHUSDT, Quantity: 0.05
- Send to your dedicated inbox.
- In your terminal, tail the email worker’s runtime logs to confirm the parse and order submission:
🔗 Next Steps
|- Alert Troubleshooting — Common TradingView webhook errors and resolutions.
|- Platform Configuration Guide — Comprehensive dictionary of all 31 env keys and 16 KV key-value items.
|- API Endpoint Reference — Review full REST payloads and HTTP error returns. 
