Connect your AI.
Bring your data.
Connect the assistant you already use over MCP, move from your old platform with an assisted migration, import a CSV any time, and use the API for everything else. Below that, the honest list of what isn't built.
The assistant you already use can run your email.
Add Email Digit to your assistant and sign in. It can find people and segments, write emails, create campaigns and read and answer replies. Every send stops for your confirmation. Only one assistant is tested end to end so far; we test each before we list it as tested.
- Claude
- ChatGPT
- Gemini
- Grok
- Perplexity
- Mistral
- Copilot
- Cursor
These tools have their own MCP servers. Connect one to the same assistant and it can work across both, for example finding this week's Stripe buyers and drafting them a thank you in Email Digit. Email Digit has no direct integration with them.
- Stripe
- Shopify
- HubSpot
- Notion
- Slack
- Zapier
We do it
with you.
About an hour on a call. You export from your current platform or give us read-only access, we bring it in, and we show you what we found before anything lands. You approve it, then we commit.
Export each audience from Mailchimp as a CSV, then import it here with column mapping onto your own fields and tags. Duplicates merge. Templates and automations are not in the file, so they are rebuilt here, not copied.
Export your profiles or a list from Klaviyo as a CSV, then import it here with column mapping onto your own fields. Duplicates merge. Flows and templates are not in the file, so they are rebuilt here, not copied.
Export your contacts from ActiveCampaign as a CSV, then import it here with column mapping onto your own fields and tags. Duplicates merge. Automations are not in the file, so they are rebuilt here, not copied.
Export your contacts from HubSpot as a CSV, then import it here with column mapping onto your own fields. This is a one-time move: two-way CRM sync is planned, not built.
Two things we do that matter: we scrub your suppression list on the way in, so anyone who previously opted out arrives unsendable rather than quietly re-subscribed. And duplicates merge rather than multiply, carrying their history with them.
What doesn't make the trip, told to you before you commit: predictive or lead scores we don't compute, platform-specific templates, and image-heavy layouts that need a light re-cut. Server-side event streams need re-pointing at our API, and we help with that.
It's assisted because we're small, and because a migration you watch is a migration you trust. It isn't a self-serve button and we're not going to draw one.
Any time, without us.
CSV import with column mapping onto your own custom fields, an optional target list, and email de-duplication that merges tags rather than creating twins, up to 50,000 rows per file. Addresses already on your do-not-send list import as unsubscribed instead of coming back sendable. CSV export of your contacts and your campaign results.
A REST API and
signed webhooks.
A REST API with scoped per-workspace bearer tokens, and HMAC-signed webhooks with a retry queue.
- →Reply received
- →Email sent
- →Email bounced
- →Domain verified or failed
- →Mailbox connected
- →Suppression created
- →Automation fired
Zapier, n8n and Make are on the roadmap.
Until they land, the webhooks and REST API cover the same ground: every event you'd want to trigger on is already available.
Two-way CRM sync is not built.
Two-way sync with HubSpot and Salesforce is planned, with field mapping. It is not built, and we're not going to describe it as though it is. What works today: import your contacts, and use webhooks to push events into whatever system you're keeping.
Tell us what would unblock you.
We'll tell you honestly whether it's near-term or not.
Migration logistics.
What's the difference between assisted, two-way and trigger?
Assisted is a one-time move off a platform you're leaving: available now, run with you. Two-way is ongoing sync with a system you're keeping: roadmap. Trigger is partner events firing our actions or the reverse: available now via webhooks and the API.
How long does a migration take?
The import itself is usually under two hours. Checking it before you cut over is the part worth not rushing.
Is there a migration fee?
No. During beta we do it with you and it's our time.
Can I run Email Digit alongside my current provider?
Yes. Campaigns here and app email elsewhere, or the reverse, while you evaluate.
Bring your list.
Keep your stack.
Start free for 15 days with no card and import your list yourself, or tell us what you're moving off and we'll do it with you.