Integrations
A short list, and every item on it works.
A wall of logos is easy to make. Here is exactly what HeySender connects to today, and how to reach everything else in the meantime.
Amazon SES
The sending engine. Connected through a role in your AWS account, with bounce, complaint and delivery feedback set up for you and checked before you send.
SMTP servers
Any SMTP server with a username and password. It sends, but it can't report bounces or complaints back, so SES stays the recommended choice.
Reoon email verification
Connect your own Reoon key to verify addresses on import, through the API or one at a time, with a policy that decides what happens to invalid, risky and disposable addresses.
Claude and other AI assistants
Through the MCP server with sign in by OAuth. Assistants can read and draft freely, and need your confirmation for anything consequential.
Your own systems, through webhooks
Signed outgoing webhooks for contact, consent, message and automation events, with retries and replay. Point them at n8n, Make, Zapier's webhook trigger or your own code.
Your own systems, through the API
Create contacts, record events, enroll people in automations and more with scoped API keys. Anything that can make an HTTP request can drive HeySender.
What is not here yet
There are no native connectors for CRMs, shops or payment platforms today, and no other sending providers besides SES and SMTP. When one ships, it goes on this page. Until then, the webhooks and the API above cover the same ground with a little glue.
If a missing connector would stop you from switching, say which one in your early access request. Those requests help decide what gets built first.
Tell us what you need to connect.
HeySender is not open for signups yet. Your request helps shape the connector list.