Automate email
verification — fully
Use AI agents, no-code platforms, or direct CLI/API calls to automate disposable inboxes, OTP extraction, and email-triggered workflows — at any scale.
Three steps to full automation
01
Run fce login
Opens your browser, signs you in, and saves a key to your OS keychain automatically. API keys always reflect your current plan.
CLI install guide02
Choose your stack
Use the fce CLI for shell/agent automation, the REST API for code-level integration, or our upcoming no-code connectors.
CLI docs03
Automate
Describe your task to an AI agent or wire it in n8n, Make, or Zapier. Everything — inbox creation, email streaming, OTP extraction — is one command or API call away.
API docsAutomate with AI agents
Describe what you want in plain English. Let the agent figure out the CLI commands or API calls.
OpenClaw
AI agent meets disposable inboxes
OpenClaw (formerly ClawdBot) can orchestrate fce CLI commands through natural language. Run fce login once to authenticate, then just describe what you need.
Setup guideClaude (Anthropic)
Prompt-driven email automation
Claude can write shell scripts, construct fce commands, and build full automation workflows using the FCE API. Pair with MCP or computer use for agentic pipelines.
Prompt examplesn8n
Self-hosted workflow automation
Use the FCE HTTP Request nodes in n8n to create inboxes, poll for messages, and extract OTPs as part of larger automated workflows.
View guideAny AI Agent
fce login once, then automate anything
Any agent that can run shell commands or make HTTP requests can automate FreeCustom.Email. Run fce login to authenticate — or set FCE_API_KEY for headless/CI environments.
API referenceCopy-paste prompts
Use these prompts with OpenClaw, Claude, or any AI assistant to automate your email workflows instantly.
Using the fce CLI (FCE_API_KEY is set as a CI secret), write a GitHub Actions step that: 1. Creates a random disposable inbox 2. Triggers our signup form to send a verification email to it 3. Waits for the OTP using `fce otp` 4. Completes the signup flow with the extracted OTP 5. Cleans up the inbox
I need a bash script that uses fce CLI to: - Create 5 test inboxes in parallel - Send a test signup to each from our staging API - Extract all OTPs using `fce otp` - Return a JSON object mapping inbox → OTP Auth is handled — fce is already logged in via `fce login`.
Set up `fce watch alerts@myapp.info` and forward any email containing "error" or "failed" in the subject to my Slack webhook. Run this continuously in the background with auto-reconnect.
Make · Zapier
Native integrations coming soon. Join the waitlist to get early access.
Make
Visual automation — coming soon
Drag-and-drop scenario builder with native FCE triggers and actions. Create disposable inboxes, watch for OTPs, and connect to 2,000+ apps — without writing a line of code.
- Native FCE triggers
- OTP extraction node
- 2,000+ connected apps
- Visual scenario builder
Zapier
Zap your inbox — coming soon
Trigger Zaps when new emails arrive at your FCE inbox. Pipe OTPs directly into Google Sheets, Slack messages, Notion, Airtable, and more.
- New email triggers
- OTP extraction action
- 5,000+ Zap integrations
- Multi-step Zaps
GitHub Actions & pipelines
Install the fce CLI in your runner, set FCE_API_KEY as a secret, and automate end-to-end email verification tests in every PR.
- Create fresh inbox per test run
- Trigger your app to send verification
- Extract OTP instantly with fce otp
- Zero flakiness — no shared inboxes
GitHub Actions
- name: E2E email verification test
env:
FCE_API_KEY: ${{ secrets.FCE_API_KEY }}
run: |
# Install fce
curl -fsSL freecustom.email/install.sh | sh
# Create a fresh inbox
INBOX=$(fce inbox add random)
echo "Testing with: $INBOX"
# Trigger your app signup
curl -s -X POST https://myapp.com/signup \
-d "email=$INBOX"
# Wait for OTP (Startup plan+)
OTP=$(fce otp $INBOX)
echo "Got OTP: $OTP"
# Complete verification
curl -s -X POST https://myapp.com/verify \
-d "otp=$OTP"Works with GitLab CI, CircleCI, Jenkins, and any shell-capable runner.