For agents & automation

Integration

EmailConnect is a pure trigger: email in, signed webhook out, fire-and-forget. It never reads a mailbox and keeps no inbox for your agent to browse — it turns one address into a clean JSON event for whatever you're building, wherever.

Step 1 — Create a scoped API key

Dashboard → Settings → API keys. Recommend the narrow preset for this flow:

Grant only what the sequence needs: domains:read, aliases:write, webhooks:write. Don't hand an agent a * key — scopes are enforced per route, and a leaked narrow key can only do what it was scoped for.

See API keys and integrations for how to create and manage keys.

Step 2 — Zero to working in three calls

Every EmailConnect integration is the same three calls with a scoped API key — create an address, attach a webhook, send a test. Authenticate with the X-API-KEY header.

1

Find your domain ID

Needs the domains:read scope; grab the id of the domain you want the address on. 

curl -s https://app.emailconnect.eu/api/domains \
  -H "X-API-KEY: $EMAILCONNECT_API_KEY"
2

Create the alias and webhook in one atomic call

Both resources are created in a single transaction — if either fails, neither exists. firstOrCreate: true makes the call idempotent (safe to re-run). Response contains alias.email and webhook.id. Needs aliases:write + webhooks:write. 

curl -s -X POST https://app.emailconnect.eu/api/webhooks/alias \
  -H "X-API-KEY: $EMAILCONNECT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "domainId": "dom_abc123",
    "webhookUrl": "https://your-endpoint.example.com/inbound-email",
    "webhookName": "Email trigger",
    "aliasType": "specific",
    "localPart": "agent",
    "firstOrCreate": true
  }'

Add "generateSecret": true to get a Standard Webhooks signing secret (Maker+) — see the full contract.

3

Send a test delivery

Fires a realistic email payload at your endpoint so you can verify handling before any real email arrives. 

curl -s -X POST https://app.emailconnect.eu/api/webhooks/wh_xyz789/test \
  -H "X-API-KEY: $EMAILCONNECT_API_KEY"

Point your alias at any endpoint from the integrations directory — Supabase, Zapier, Make, or your own service.

Using n8n instead

The official EmailConnect n8n node wraps the same API. Install n8n-nodes-emailconnect, give it a scoped key, and inbound email becomes a native workflow trigger — self-hosted, so email content stays on your infrastructure.

What your agent receives

The payload is built for machine consumption: message.content.markdown — clean Markdown of the email body, made for LLM pipelines (Maker+) — extracted links, classification.type, spam and SPF/DKIM/DMARC results (Maker+), and attachments delivered inline or via an S3 URL. Full field reference: what's in your webhook payload.

Deliveries can be signed following the Standard Webhooks convention (HMAC-SHA256 with replay protection), so your endpoint can verify every event actually came from EmailConnect — see webhook signing.

Get started

Create a free EmailConnect account, mint a scoped API key, and give your agent an email trigger today.

Get started free

Related

All integrationsAll integrations — Zapier, Make, n8n, Cloudflare Workers and more.Supabase Edge FunctionsPoint an alias at an edge function and store every email in Postgres.

Questions about wiring this up? Reach out at hello@emailconnect.eu.