IntegrationEmail / Marketing destination
Resend Integration - Send Transactional Emails from Product Events
Meshes routes product events into Resend through segment membership changes and template-based email sends. That means one signup event can send the welcome email immediately while CRM and lifecycle tools update in parallel from the same Meshes delivery layer.
user.signuppayment.failedtrial.expired|Actionsadd_to_segmentremove_from_segmentsend_email_templateThe event names shown here are examples. In Meshes, event types are fully customized for each organization.
What you can do
Supported actions with real product context behind them
Create the Resend connection in Meshes with an API key. Meshes loads the available segments and templates from that Resend account so rules can target live email resources and optionally override subject or from values for template sends.
Email feels straightforward until it has to stay reliable across retries, partial outages, multiple product-triggered templates, and fan-out to the rest of the stack. Signup, billing, and lifecycle events usually matter to more than one destination at once.
Meshes keeps Resend inside the same event-routing layer you already use for CRM, lifecycle, support, and alerts. One user.signup event can trigger a welcome email in Resend while another rule adds the contact to the active-member follow-up sequence or updates CRM context in parallel.
add_to_segmentAdd contacts to Resend segments
Use lifecycle and qualification events to move contacts into the segment that should receive the next campaign or notification.
remove_from_segmentRemove contacts from segments when state changes
Keep Resend segmentation accurate when the customer no longer belongs in the original audience.
send_email_templateSend template-based email directly from the event
Trigger transactional or lifecycle email templates when the product event means the customer should receive a message immediately.
Common use cases
How Meshes teams usually put Resend to work
These are the workflows where this destination tends to matter first. The point is to keep the product event, the destination action, and the operational retry path in one place.
Send the welcome email and update follow-up systems from signup
Use user.signup to trigger a Resend welcome template while HubSpot, ActiveCampaign, or another destination updates the follow-up sequence from the same event.
Send billing and recovery email on payment failures
Use payment.failed to trigger a Resend template with the account context the customer needs right away.
Send trial reminders and conversion prompts
Use trial.expired and related lifecycle events to send timely follow-up through Resend without a separate email worker.
Keep email delivery on the same event bus as everything else
Let the same event emission path drive email, CRM, lifecycle lists, support, and alerts in parallel instead of branching into a custom send service.
How it works
Connect the destination, define the rule, emit the event
In Meshes, the operating model is simple: create the connection in the workspace, create the rule, then let the event delivery layer handle the last mile.
Connect Resend
Create the Resend connection in Meshes with the API key and confirm the segments and templates you need are visible in the connection action data.
Create routing rules in Meshes
Create rules for events like user.signup, payment.failed, or trial.expired, choose a segment action or send_email_template, and map the payload fields the template expects.
Emit the event and review delivery
Emit the event from your product or use Send Test Event in Meshes. Meshes delivers the Resend action, retries transient failures, and keeps full delivery history for replay while other destination rules can run in parallel from the same event.
Event example
Emit the product event once
import MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'user.signup',
resource: 'user',
resource_id: 'usr_2048',
payload: {
email: 'alex@northstar.io',
first_name: 'Alex',
last_name: 'Nguyen',
plan: 'starter',
source: 'website',
},
});Connection model
API key
Create the Resend connection in Meshes with an API key. Meshes loads the available segments and templates from that Resend account so rules can target live email resources and optionally override subject or from values for template sends.
Why Meshes
Why teams use Meshes for Resend
The benefit is not just that the destination is supported. It is that the destination sits inside the same fan-out, retry, replay, and delivery-visibility layer as the rest of your stack.
Welcome and transactional sends stay event-native
Meshes lets the product event trigger the Resend template directly, so signup, billing, and lifecycle communication is tied to the moment the state changed.
You get visibility into every attempt
If a message fails because of downstream API issues or mapping mistakes, the event history makes that visible and replayable.
Templates and segments can share one connection
The same Resend connection can support both direct email sends and audience management without adding separate delivery infrastructure.
Email can fan out with CRM and lifecycle updates
A signup event rarely affects only email. Meshes lets the same event trigger the Resend welcome template while CRM and lifecycle tools update the follow-up path in parallel.
Keep exploring
Related guides, use cases, docs, and comparison pages
These links are the next layer down: concrete patterns, supporting documentation, and the build-vs-buy context that usually comes up during evaluation.
Catalog
All integrations
Return to the integrations catalog and compare Resend with the rest of the Meshes email and lifecycle destinations.
Open linkDocs
Resend docs
See the Meshes setup flow, supported actions, and rule-building details for Resend.
Open linkUse Case
User signup fan-out
See how one signup event can send the welcome email, update CRM, and add the contact to the right follow-up sequence in parallel.
Open linkUse Case
Payment failed notifications
See how payment.failed can drive alerts, CRM updates, support context, and email from the same event.
Use Case
Trial expiry notifications
See how lifecycle deadlines can reach the systems that need to act before a customer drops out.
Open linkGuide
Browse routing guides
See more Meshes patterns that can be adapted for transactional email and lifecycle delivery.
Open linkCompare
Meshes vs. DIY
See what it takes to own transactional email retries, replay, and per-destination observability yourself.
Open link