[{"data":1,"prerenderedAt":13},["ShallowReactive",2],{"$fMWt2lvcLzvtg026ZXYN2AJn-AZfCq0Lg17vN5m9FEL0":3},{"title":4,"slug":5,"excerpt":6,"category":7,"order":8,"screens":9,"html":12},"Integration guides","integration-guides","Step-by-step guides for connecting EmailConnect to Supabase, automation platforms, AI agents, and any other HTTP endpoint","integrations",4,[10,11],"webhooks","aliases","\u003Cp>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.\u003C\u002Fp>\n\u003Ch2>The integrations directory\u003C\u002Fh2>\n\u003Cp>The \u003Ca href=\"\u002Fintegrations\u002F\">integrations directory\u003C\u002Fa> lists the platforms we see most across live aliases, with step-by-step guides:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ca href=\"\u002Fintegrations\u002Fsupabase-edge-functions\u002F\">Supabase Edge Functions\u003C\u002Fa>\u003C\u002Fstrong> — 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"\u002Fintegrations\u002Fagents\u002F\">For agents & automation\u003C\u002Fa>\u003C\u002Fstrong> — trigger Claude-, ChatGPT- or n8n-driven automations from email with a scoped API key and three REST calls.\u003C\u002Fli>\n\u003Cli>More platforms (Zapier, Make, Cloudflare Workers, Google Apps Script, and others) are listed with guides on the way.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Using a platform we haven't covered yet? Tell us at \u003Ca href=\"mailto:hello@emailconnect.eu?subject=Integration%20request\">hello@emailconnect.eu\u003C\u002Fa> and we'll write the guide.\u003C\u002Fp>\n\u003Ch2>The setup is always the same\u003C\u002Fh2>\n\u003Cp>Whatever the receiving end, every integration follows the same three steps:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Create an alias\u003C\u002Fstrong> — on your own domain, or your system alias that works without any DNS setup.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Attach a webhook\u003C\u002Fstrong> — the URL of your endpoint. Programmatically, both happen in \u003Ca href=\"\u002Fhelp\u002Fwebhook-alias-atomic-endpoint\u002F\">one atomic API call\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Send a test\u003C\u002Fstrong> — deliver a realistic payload to your endpoint before any real email arrives.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Related\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fwebhook-payload-reference\u002F\">What's in your webhook payload\u003C\u002Fa> — the JSON your endpoint receives\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fapi-keys-integrations\u002F\">API keys and integrations\u003C\u002Fa> — scoped keys for programmatic setup\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fwebhooktest-integration\u002F\">Testing webhooks with WebhookTest\u003C\u002Fa> — zero-code end-to-end testing\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fwebhook-signing\u002F\">Webhook signing\u003C\u002Fa> — verify deliveries really came from EmailConnect\u003C\u002Fli>\n\u003C\u002Ful>\n",1783520834614]