OpenClaw
This guide preserves the legacy OpenClaw integration target. Review the package name and OpenClaw command syntax before publishing.
Requirements
- OpenClaw installed.
- Mailtarget API access.
- A verified company sending domain.
- A backend or trusted agent environment that can hold
MAILTARGET_API_KEY.
Legacy setup pattern
Legacy docs install a Mailtarget Email skill:
clawhub install mailtarget-email
Then configure the API key in the trusted runtime:
openclaw env set MAILTARGET_API_KEY="your_api_key_here"
or:
export MAILTARGET_API_KEY="your_api_key_here"
Domain automation boundary
Legacy docs describe an autonomous flow where an agent creates sending domains, reads DNS records, updates Cloudflare, verifies the domain, and sends a test message. Keep that workflow behind an explicit approval step.
Recommended guardrails:
- Require a human approval before DNS writes.
- Restrict the domain list the agent can modify.
- Store Cloudflare and Mailtarget credentials separately.
- Log every DNS and sending-domain action.
- Verify the domain before allowing production sends.