Unitpost
Integrations · Soon

Plug into the tools you already use

Connectors for the platforms, frameworks, and data sources you already run.

Join the waitlistBrowse guides
No-code
Workflow
Warehouse
Frameworks
CLIs
CMS
Platforms
SDKs
& more

How it works

Connectors, not glue code

Verified domains and scoped keys. Contacts and events both ways.

No-code connectors

First-class connectors. Not Zapier hops.

Sync from your warehouse

Contacts and events from your warehouse. No custom pipeline.

App frameworks

Sending email is a config step.

Reuse keys & domains

Verified domains and scoped keys. Nothing to re-provision.

Built on the public API

Anything a connector can do, your code can too.

Questions

Common questions

Does Unitpost have prebuilt integrations or connectors?

Not yet — first-class connectors are on our roadmap, and this page describes what's planned rather than what you can install today. What does ship now covers most stacks: a REST API at /api/v1, official Node, Python, and Ruby SDKs, an SMTP relay, a hosted MCP server for AI agents, and signed webhooks for events flowing back to you.

How do I connect a tool that only speaks SMTP?

Point it at smtp.unitpost.com with the username unitpost — that literal string, not your email — and a Unitpost API key carrying emails:send as the password. Use port 587 or 2587 for STARTTLS, or 465 or 2465 for implicit TLS; TLS is required. WordPress, Supabase, Nodemailer, Rails, Laravel, Django, and Auth0 all work this way, with guides for each.

Do SMTP sends behave the same as API sends?

Yes — SMTP is a second front door to the same pipeline, not a separate system. Messages pass the same verified-domain gate, quotas, and suppression checks, and they emit the same delivery, bounce, complaint, open, and click events to your dashboard and webhooks. You can even set a Unitpost-Idempotency-Key MIME header to get the same 24-hour dedupe as the REST API.

Will a connector be able to do something my own code can't?

No, and that's deliberate. Every connector is planned to sit on the same public /api/v1 surface, so anything an integration can do is reachable from your own code, an SDK, or an MCP client — and it stays bounded by the scopes on whichever API key you hand it. There's no privileged internal path a connector gets and you don't.

Can an AI agent wire up Unitpost for me today?

Yes, that part is already live. Our hosted MCP server exposes one tool per API operation to any MCP client such as Cursor, Claude, Codex, or Copilot, so an agent can send mail, verify a domain, or build a segment directly. The open-source Unitpost agent Skill separately teaches a coding agent our API shape, scopes, and send-safety rules. Install both.