Email from records; log customer sends
Connect
SPIRITT
ResendResend email
With follow-through
SPIRITT builds and runs the operation around your Resend emails, from reusable templates and recipient segments to event-driven follow-through. Connect product activity to the right message and keep exceptions moving toward resolution.
What you can do with Resend.
Messages tied to real work
Send transactional emails from product or billing milestones, with recipient checks and a send history that prevents duplicate follow-ups.
A maintained email library
Create, duplicate, update, and publish Resend templates so onboarding, receipts, and service notices stay aligned with your product.
Events that lead to action
Connect Resend email events to an exception queue, customer context, and team alerts instead of leaving delivery issues unexplained.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the transactional email, contact operations, or customer communication you want to delegate.
02
Connect Resend
Connect Resend with an API key that has access to the email, contact, template, and domain resources your mission needs.
03
Delegate an outcome
Give SPIRITT a concrete email mission, including recipient rules and message content. It builds the workflow and runs it within your authorized scope.
Hand over a mission.
Choose a mission. Make it yours.
Put Resend to work.
Put your email operation to work
Questions
Resend, with SPIRITT.
01What email work can SPIRITT perform in Resend?+
SPIRITT can send individual and batch emails, retrieve sent email details and attachments, update or cancel scheduled emails, and create and maintain reusable templates. It can also manage contacts, segments, topics, domains, and email event webhooks. Batch sends support up to 100 emails per request.
02What access does Resend need, and how are sends controlled?+
Resend connects through an API key. Its permissions determine which resources SPIRITT can use. Confirm recipients and message content before sending, including the rules for recurring sends. A newly created sending domain remains unverified until its DNS requirements are met and verification succeeds.
03Can SPIRITT run recurring transactional email workflows?+
Yes. SPIRITT can build the surrounding workflow to select eligible recipients, send through Resend, store email IDs, and reconcile the results on a schedule. Resend webhooks can feed available email events into that workflow, while a send ledger helps prevent duplicate messages when a run resumes.
04How can Resend work with my product and billing tools?+
Supabase account records can supply welcome email context, Stripe payment records can drive confirmation messages, and HubSpot lifecycle stages can determine contact segment membership. SPIRITT coordinates those sources with Resend sends and routes unresolved exceptions to tools such as Slack.
05Can SPIRITT build a support view of our Resend emails?+
Yes. It can build a customer timeline from sent emails, individual email details, and available sent attachment metadata. It can also use Resend's received-email list for intake workflows. That receiving access is specific to Resend, not unrestricted access to Gmail, Outlook, or customers' inboxes.
06Is sending an email the same as launching a Resend broadcast?+
No. The available actions support sending individual or batch emails, but broadcast actions cover listing, retrieving, creating drafts, and updating broadcasts. SPIRITT can prepare a targeted draft broadcast and verify its content; those actions do not provide broadcast sending.