Integrations overview
EmailFlow AI connects to the rest of your stack from one place: Integrations in the sidebar. Every integration lives in a single directory — what it does, whether it is connected, and where to set it up — and the same catalog is published at emailflow.ai/integrations.
How the directory works
Integrations are grouped by what they do for you:
- Destinations — places EmailFlow AI pushes to: ad platforms (Meta, Google, TikTok, LinkedIn audience sync), signed webhooks, and template export to Mailchimp, Klaviyo, and HubSpot.
- Data sources — systems that feed your audience and automations: your WooCommerce store, Stripe billing events, and Shopify store events including abandoned carts.
- Design — creative inputs like Figma frame import (planned).
- Auth & user management — user-base sync from providers like Clerk (planned).
Each card tells you exactly one of three things:
| Badge | Meaning |
|---|---|
| Included | Built into every account with nothing to connect — managed Amazon SES delivery and Stripe-powered checkout. |
| Connected | Your account has a live connection. The button switches to Manage and takes you to that integration's settings. |
| Coming soon | On the roadmap but not shipped. The card carries a one-click request button so you can tell us it matters to you. |
Connecting an integration
Click Connect on any available card. You are taken to the integration's own setup surface — ad platforms use OAuth (you approve access on the platform's site and are returned here), websites use a small embed script, and webhooks take an endpoint URL. Once connected, the directory shows the green Connected badge and the card's button becomes Manage.
Why is there no "connect your ESP" option for sending?
Delivery is deliberately not an integration you configure. Every plan sends through our managed Amazon SES infrastructure — warmed IPs, DKIM signing, bounce and complaint processing, and reputation monitoring are all handled for you. The only setup is verifying your sending domain. Read more in Amazon SES infrastructure.
Requesting an integration
The directory only lists what exists or what we genuinely plan to build — no vaporware. If the tool you need is missing, use Request an integration at the bottom of the page: it opens a prefilled support ticket, and requests directly shape which connectors we build next.