email·digit
Integrations

Bring your stack.
Or leave it. Up to you.

Email Digit replaces your ESP and your deliverability tool — and plays nicely with the CRM / CDP / automation layer you already have. Move what you want; sync what stays.

By category

Four shapes of
integration.

Migration tooling for moving off an existing ESP. CRM + CDP for ongoing two-way sync. Workflow automation for everything else.

How we think about integrations

Reversible by default.
Honest about coverage.

Our default integration philosophy follows two rules: every integration must be reversible (no lock-in), and we say up-front what doesn't move. Migration tooling that silently drops engagement history isn't migration — it's a one-way door.

  • Every migration is reversible. Export your data anytime, in the same format you imported it. We don't hide your contacts behind our format.
  • Honest caveats per partner. Every sub-page lists what won't come across — Klaviyo's predictive scores, Mailchimp's image-heavy templates, ActiveCampaign's pipelines. No surprises post-cutover.
  • Hand-help during beta. The migration UI is Q3 2026 — until then, every migration runs on a 1-hour screen-share with us driving.
  • Two-way sync, not lock-in. CRM integrations sync both directions. If you leave Email Digit, your data is already in your CRM — we've been writing it there.
  • Native API for everything else. If we don't have a partner integration, our REST API + webhooks cover the ground. See the docs.
Missing one?

Tell us what to build next.

We add 2–3 new integrations per quarter, prioritized by what beta customers ask for. Tell us what you need and we'll tell you if it's already in the queue.

Request integration Most-requested in the pipeline: Notion · Linear · Slack · Discord · Pipedrive · Front
FAQ

Integration logistics.

What's the difference between import, two-way, and trigger integrations?

Import — one-time migration FROM the partner INTO Email Digit. Used for ESPs you're leaving. Two-way — ongoing bidirectional sync. Used for CRMs you're keeping. Trigger — partner events fire Email Digit actions (or vice versa). Used for workflow tools like Zapier / n8n / Make.

Do I need to build anything to use an integration?

Migration integrations: no — we run them on a screen-share during beta. Two-way: a 30-second connect flow in /dashboard. Workflow automation: depends on the workflow tool, but typically just an API token paste.

Can I use Email Digit alongside my existing ESP?

Yes — for specific use cases. Most teams cut over completely within a month, but some keep their existing ESP for transactional sends while running campaigns through us, or vice versa. We'll help you architect whichever shape makes sense.

How long does a typical migration take?

The actual data import: 30 minutes to 2 hours depending on workspace size. The QA + cutover: 1–3 days. Most teams are sending real campaigns through Email Digit within a week of starting the migration conversation.

Is there a migration fee?

No. During private beta we cover the cost (it's our time, on a screen-share). Beta customers get a $500 migration credit that lands on the first paid month. Post-beta the credit goes away but the migration help is still free.

Integrations

Bring your stack.
We'll meet it where it is.

Request access. Tell us what you're moving from or what you're keeping alongside. We'll architect the shape that fits.