SendPost Integrations: Native, Zapier, and API
SendPost has no app marketplace. The catalogue is 6 third-party sending-provider integrations, 2 migration APIs, 6 official SDKs and 11 reference apps from the 43 repositories in the github.com/sendpost organisation. There is no app on Zapier, Make or n8n and no official WordPress, Shopify or WooCommerce plugin, anything that is not SMTP runs on the REST API and webhooks. SendPost is infrastructure sitting under a marketing ESP; its sibling SendX holds the marketing connectors.
At a glance
Integrations directory
These 28 entries are everything SendPost publicly documents or ships. Only the first two categories involve someone else’s product; the rest is SendPost’s own code, listed because with no plugin to install, a working Laravel or Workers example is the connector. Docs at docs.sendpost.io, code at github.com/sendpost. The feature page claims SDKs in over 14 languages; only 6 repositories exist.
Sending providers. TPSP (6)
A TPSP (third-party sending provider) is SendPost’s core idea: keep your account with SendGrid, Amazon SES, Mailgun, Postmark or SparkPost and let SendPost be the control plane above it. Upstream plan limits still govern throughput.
The most misread page in the docs. “Custom SMTP Integration” is not where relay credentials live. It asks for your own MTA hostname and credentials so SendPost can relay through your infrastructure, traffic flows the other way. The relay you want is smtp.sendpost.io, ports 25, 587 and 2525 for STARTTLS, 465 for SSL.
Route through your existing SendGrid account; SendPost owns the API.
Your own Amazon SES account as the delivery backend.
Route sends through an existing Mailgun account, events consolidated.
Connect an existing Postmark account for routing and reporting.
An existing SparkPost account as a managed delivery backend.
Relay via your own Postfix or compliant MTA plus an event agent.
DKIM signing happens before the message reaches your provider, so signature and verified domain stay consistent whichever backend carries it. On the custom-SMTP path a failing server is retried 5 times with linear backoff (1h to 5h) before SendPost emits CSDropped-no terminal signal for up to 15 hours. Alert on it explicitly.
Migration & compatibility APIs (2)
Two API surfaces shaped like other vendors’ so existing code can be repointed, not rewritten. Shims, not clones.
Drop-in SendGrid-shaped endpoint for existing SendGrid code.
SES-shaped surface for migrating without rewrites.
The known gap is templates: a SendGrid template_id returns 400 because the shim expects inline content or a native template, and that rework is usually most of the migration. Requests above 30 MB return 413, a ceiling belonging to this endpoint rather than the native API. For a straight provider swap, compare Postmark, Resend and MailerSend.
Transport, events & notifications (4)
Wired up whichever backend carries the mail: native relay, webhook stream, log-parsing agent, alerting.
Native relay at smtp.sendpost.io: ports 25/587/2525 TLS, 465 SSL.
Signed callbacks for delivery, open, click, bounce and complaint.
Agent beside your MTA parsing logs and reporting events back.
Deliverability alerts into Slack; named on the product page, undocumented.
With no Zapier app, webhooks carry the automation weight: bounces into a CRM, pausing on a complaint spike, mirroring events into a warehouse. Budget for a receiver you host and verify signatures on. The event agent uses its own ingestion key, not your SendPost API key.
Official SDKs (6)
Six first-party clients, all pushed within days of each other in late December 2025-a generated release, not six maintained libraries.
Official client: npm install sendpost-js-sdk.
Official Python client; import sendpost_python_sdk.
go get github.com/sendpost/sendpost-go-sdk.
Official Ruby client, distributed as a gem.
Official Java client via Maven or Gradle; see README.
Official PHP client, updated December 29, 2025.
Framework reference implementations (5)
The closest thing to a one-click integration: copy the mail-service layer, not the whole app. Laravel, Django and Rails also ship SMTP mailers, so pointing the framework transport at smtp.sendpost.io stays valid.
Official reference app for Django.
Official reference app for Laravel.
Official reference app for sending email from Rails.
Official reference app for NestJS.
Official reference app for Spring Boot.
Serverless reference implementations (5)
Edge runtimes are where SMTP stops being an option, port 587 is unavailable on Cloudflare Workers. All five use the HTTP API.
Node.js and Python examples for Lambda.
Official reference app for Vercel Functions.
Official reference app for Netlify Functions.
Official reference app for Cloudflare Workers.
Official reference app for Supabase Edge Functions.
What is missing, stated plainly. No Zapier, Make or n8n app. No official WordPress, Shopify or WooCommerce plugin. No CRM, forms or analytics connectors. No MCP server, official or community, as of August 2026. WordPress users can still send through the relay with dashboard credentials in a generic SMTP plugin, because SMTP is a standard, not because SendPost ships a plugin.
Frequently asked questions
Does SendPost have a Zapier integration?
No, and none on Make or n8n either. The confusion comes from the sibling product: SendX, the marketing ESP built by the same team, does have a Zapier app. SendPost automation runs on the REST API and signed webhooks, so anything you would build with a no-code connector needs a receiver you host.
Can SendPost send through my existing SendGrid or Amazon SES account?
Yes, and it is the product’s central design. SendGrid, Amazon SES, Mailgun, Postmark, SparkPost and any standards-compliant MTA can act as third-party sending providers. You keep the upstream account and contract; SendPost sits in front as one API, one event stream, one reputation view.
What is a TPSP in SendPost and when should I use one?
TPSP means third-party sending provider, an external delivery backend SendPost routes through instead of its own relay. Use one when you have committed volume or warmed IP reputation with an incumbent, want to spread risk across backends, or are an ESP isolating tenants. With no incumbent, send through smtp.sendpost.io directly.
Does SendPost work with Laravel, Django, or Rails?
Yes, through official example repositories for all three plus NestJS and Spring Boot. There is no framework package to install, they are runnable apps you copy the mail layer from. Because all three ship an SMTP mailer, you can also point the existing transport at smtp.sendpost.io on port 587 and skip the SDK.
Can I use SendPost from AWS Lambda or Cloudflare Workers?
Yes. Official examples exist for AWS Lambda (Node.js and Python), Vercel Functions, Netlify Functions, Cloudflare Workers and Supabase Edge Functions. All use the HTTP API rather than SMTP: Cloudflare Workers cannot open outbound SMTP connections at all, and holding a session open in a short-lived function is unreliable.
What is the difference between SendX integrations and SendPost integrations?
Sibling products under the same parent, SendWorks, with a clean division of labour. SendX is the marketing ESP: campaigns, lists, automation and the connector catalogue, including a Zapier app. SendPost is the infrastructure: email API, SMTP relay, sub-accounts, dedicated IPs, provider routing. Hunting a CRM connector? Wrong page.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
