Integrations
Integrations
Send from the frameworks, automation tools, notification platforms and CMSes you already use. Every card links to its docs.
Automation
Send email from workflows with an HTTP request step, or a community node in n8n.
- n8nPackageA community node that sends email, with templates, scheduling and idempotency keys.
- ZapierAPISend email with a Webhooks by Zapier POST to the Groundmail API.
- MakeAPISend email with the HTTP app's Make a request module.
- Pabbly ConnectAPISend email with the API by Pabbly action.
- PipedreamAPISend email from a Node.js code step or an HTTP request step.
- IntegratelyAPISend email with the Webhook/API action.
Notification platforms
Keep your notification workflows and route their email through our SMTP relay.
Frameworks and libraries
Official SDKs, mail transports and auth packages for the stack you already use.
- Next.jsNode SDKSend from Route Handlers, Server Actions and background jobs.
- Node.jsNode SDKUse the SDK in Express, Fastify, workers and queue consumers.
- NodemailerPackageA Nodemailer transport that sends over the HTTP API.
- React EmailNode SDKWrite components, preview them locally and send them with the SDK.
- NestJSPackageRegister one client and inject it into any provider.
- AdonisJSPackageA mail transport for @adonisjs/mail.
- RailsPackageAn Action Mailer delivery method in the groundmail gem.
- LaravelPackageA Mail transport: set MAIL_MAILER=groundmail.
- SymfonyPackageA Symfony Mailer transport over the HTTP API.
- Python SDKPackagepip install groundmail.
- Go SDKPackageUse the Go SDK in HTTP handlers, workers and cron jobs.
- PHP SDKPackagecomposer require groundmail/groundmail.
- Ruby SDKPackagegem install groundmail.
- Better AuthPackageSend verification, password reset and magic-link email with a drop-in package.
- Auth.jsPackageAn email provider for Auth.js and NextAuth magic links.
- ClerkPackageSend Clerk's verification codes and magic links through Groundmail.
CMS and e-commerce
Send site, store and order email from your own domain.
- WordPressSMTPPoint WP Mail SMTP or FluentSMTP at the Groundmail relay.
- WooCommerceSMTPSend order and account emails through the same SMTP setup.
- PayloadPackageAn email adapter for Payload 3.
- StrapiPackageAn email provider for Strapi 4 and 5.
- MedusaPackageThe email channel of Medusa's Notification Module.
AI and agents
Add email to apps built with AI tools, and let your coding agent do the setup.
- MCP serverMCPLet Claude, ChatGPT, Cursor and other MCP clients send email and manage domains.
- Cursor rulesGuideA project rule that teaches Cursor's agent how to use Groundmail.
- Agent SkillsGuideSkills for Claude Code, Cursor, Codex and other agents.
- LovableGuideStore your key as a secret and paste a prompt.
- ReplitGuideUse MCP while building and Secrets for the running app.
- BoltGuideA .env secret and a chat prompt for Bolt apps.
- v0GuideSend from a Route Handler or Server Action in a v0 app.
- Base44GuideUse your own domain for Base44 app email.
Data and no-code
Send from spreadsheets and backends-as-a-service.
Alerts
Get told when something needs attention, and add SMS to your flows.
DNS providers
Publish your sending domain's records in one click.
Not listed?
If a tool can make an HTTP request, it can use the REST API. If it has SMTP settings, point it at the SMTP relay. For what each integration does, see integrations in the feature overview.
Common questions
What if my tool isn't listed?
Anything that can send an HTTP request can call the REST API: POST https://api.groundmail.dev/emails with an Authorization: Bearer gm_… header and a JSON body. Anything with SMTP settings can use smtp.groundmail.dev on port 587 (STARTTLS), with the username groundmail and an SMTP credential as the password.
Should I use the API or SMTP?
Use the API or an SDK when you can: you get idempotency keys, scheduling, templates and structured errors. Use SMTP for tools that only offer SMTP fields, such as WordPress, Knock, Courier and Novu. SMTP mail goes through the same domain checks, suppressions, limits and webhooks as the API.
How do I test an integration without emailing real people?
Use a test key (gm_test_…), which runs every check but delivers nothing, or send to a simulator address such as delivered@simulator.groundmail.dev or bounce@simulator.groundmail.dev. Simulator addresses also work over SMTP and produce real webhook events.
Do integrations cost extra?
No. Integrations aren't priced separately. What you send counts toward your plan like any other email.
Put your transactional email on solid ground.
Start free on our transactional pool. Move to dedicated IPs or a dedicated server when you need the isolation. Same API either way.