Route domain and delivery issues to owners
Connect
SPIRITT
MailerSendMailerSend
Own delivery operations
SPIRITT turns MailerSend domain checks, sent-message logs, and webhook events into a working email operations system. Catch setup gaps, investigate missing messages, and give your team a clear path to resolution.
What you can do with MailerSend.
Launch with fewer gaps
Prepare sending domains, provision application access, and connect delivery webhooks so each application has a traceable operational setup.
Resolve delivery questions
Bring sent-message records and captured delivery events into one support view, with evidence and next steps for each reported missing email.
Keep events useful
Build delivery event workflows around domain webhooks, connect incidents to team tools, and keep API usage visible as the operation grows.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for transactional email readiness, delivery investigations, or ongoing messaging operations.
02
Connect MailerSend
Connect MailerSend with an API key whose permissions cover the domains, records, and setup actions your mission needs.
03
Delegate an outcome
Ask SPIRITT to build a delivery desk, prepare a sending domain, or run recurring checks that turn email issues into owned work.
Hand over a mission.
Choose a mission. Make it yours.
Put MailerSend to work.
Give email delivery an operator
Questions
MailerSend, with SPIRITT.
01Can SPIRITT send emails through this MailerSend connection?+
The available actions cover domain and access setup, webhooks, templates, recipients, and message records, but not email sending. SPIRITT can build and operate the readiness and delivery-support systems around your application's sending flow; it does not treat this connection as a send-email action.
02What access does MailerSend require?+
MailerSend connects with an API key. Its permissions determine which records SPIRITT can inspect and which setup actions it can perform. For application provisioning, SPIRITT can also create domain-scoped API tokens and SMTP users when the connected key permits those actions.
03Can it verify a new sending domain for me?+
SPIRITT can create a sending domain and retrieve its DKIM, SPF, MX, and tracking verification status. DNS changes require access to the system that hosts your DNS; this connection does not provide DNS editing. SPIRITT can coordinate that work and recheck MailerSend for the resulting verification status.
04How can delivery events reach our other systems?+
SPIRITT can create, list, and delete MailerSend domain webhooks and build a receiver for sent and delivered event notifications. It can store captured events in Supabase, bring actionable exceptions to Slack, and coordinate investigation tasks in Asana. Recurring checks can close application-handoff cases when subsequent sent-message evidence arrives, while tracking delivery as a separate outcome.
05What custom tools can SPIRITT build around MailerSend?+
Useful builds include a recipient investigation console, a domain migration exception ledger, a searchable template catalog, and an API quota dashboard. These combine available MailerSend records and setup actions with your application requirements rather than assuming the integration can edit templates or resend messages.
06Does the integration also cover MailerSend SMS?+
SPIRITT can inspect SMS activity, sent messages, phone numbers, recipients, and inbound route configurations. That supports delivery investigations and routing reviews. The available SMS actions do not include sending messages, purchasing numbers, or changing inbound routes.