Integration guides
EmailConnect delivers every email as structured JSON to any HTTP endpoint — so it works with whatever your stack already speaks: serverless functions, automation platforms, your own API routes, or an AI agent's workflow.
The integrations directory
The integrations directory lists the platforms we see most across live aliases, with step-by-step guides:
- Supabase Edge Functions — the most common pattern among EmailConnect users: point an alias at an edge function and store every email in Postgres, with attachments in Storage. Complete working code.
- For agents & automation — trigger Claude-, ChatGPT- or n8n-driven automations from email with a scoped API key and three REST calls.
- More platforms (Zapier, Make, Cloudflare Workers, Google Apps Script, and others) are listed with guides on the way.
Using a platform we haven't covered yet? Tell us at hello@emailconnect.eu and we'll write the guide.
The setup is always the same
Whatever the receiving end, every integration follows the same three steps:
- Create an alias — on your own domain, or your system alias that works without any DNS setup.
- Attach a webhook — the URL of your endpoint. Programmatically, both happen in one atomic API call.
- Send a test — deliver a realistic payload to your endpoint before any real email arrives.
Related
- What's in your webhook payload — the JSON your endpoint receives
- API keys and integrations — scoped keys for programmatic setup
- Testing webhooks with WebhookTest — zero-code end-to-end testing
- Webhook signing — verify deliveries really came from EmailConnect