• Use Cases
  • Pricing
  • Security
  • Docs
Sign InStart free

The outbound integration layer for SaaS products: emit once, then let Meshes handle routing, retries, fan-out, and delivery history.

  • Terms of Service
  • Privacy Policy
  • Acceptable Use Policy
  • Cookie Policy

© Copyright 2026 Meshes, Inc. All Rights Reserved.

  • Getting Started
    • What is Meshes?
    • Quickstart
    • Core Concepts
    • API Overview
  • AI Tools
    • Cursor Rules
    • MCP Server
    • LLMs Docs
  • API Documentation
    • API Reference
    • Authentication
    • Results
    • Rate Limiting
    • SDKs
    • Integrations & Rules
  • Events
    • Publishable Keys
    • Send Events
    • Bulk Event Ingestion
  • Embed & Sessions
    • Quickstart
    • Session API Overview
    • Launch URL and Iframe Bootstrap
    • Iframe Message Contract
    • Session Roles and Scopes
    • Workspace Pages Available in Embed
    • Session Refresh Lifecycle
    • Iframe Sizing and Resize Handling
    • OAuth and Connection Setup Behavior
    • Security Model
    • Troubleshooting
  • Integrations
    • ActiveCampaign
    • AWeber
    • HubSpot
    • Intercom
    • Mailchimp
    • MailerLite
    • Resend
    • Salesforce
    • Slack
    • Webhooks
    • Zoom

Resend

Use Meshes to manage Resend segments and send template emails from product events.

Use the Resend integration when one product event should update lifecycle state and send an email in the same flow. In a Meshes workspace, you create the Resend connection, build a rule for the event you care about, and choose whether the rule should update a segment or send a template email.

Supported actions

  • Add to Segment upserts the contact and adds that contact to a selected Resend segment.
  • Remove from Segment upserts the contact and removes that contact from a selected Resend segment.
  • Send Email sends a selected Resend email template, with optional subject and from overrides.

Create the connection

  1. Open Connections in your Meshes workspace.
  2. Click New Connection.
  3. Select Resend.
  4. Give the connection a clear name.
  5. Enter the API Token from Resend.
  6. Save the connection.

Create a rule

  1. Open Rules and click New Rule.
  2. Select the event type that should trigger the Resend action, such as user.signup or trial.started.
  3. Select the resource type for that event.
  4. Choose your Resend connection.
  5. Select Add to Segment, Remove from Segment, or Send Email.
  6. Choose the segment or email template.
  7. If you use Send Email, set subject and from overrides only when you want to override the template defaults.
  8. Map the event fields Meshes should send to Resend.
  9. Save the rule.

The mapping catalog includes email, firstName, lastName, contact properties from Resend, and a template_variables object for template sends.

Use template_variables to send the replacement values that the selected Resend email template expects. Each key inside template_variables should match a variable used by that Resend template. If the template uses values such as firstName and plan, map those values into template_variables.firstName and template_variables.plan in Meshes so Resend can render the final email content.

Send a test event

Send a test event in Meshes

Use Send Test Event on the rule to verify the segment or email action.

{
  "email": "test@example.com",
  "first_name": "Test",
  "last_name": "User",
  "template_variables": {
    "firstName": "Test",
    "plan": "growth"
  }
}

In this example, template_variables.firstName and template_variables.plan are the values Resend uses to replace those variables when it renders the selected email template.

Review results

After the event runs, open Events and inspect the Resend delivery details. Meshes shows whether the rule completed, what action ran, and any retries or failures.

Notes

  • Resend segments and templates are loaded from the connected account.
  • Resend actions upsert the contact before segment or template delivery runs.
  • Use template_variables for the actual replacement values the selected Resend template should render in the outgoing email.
  • subject and from overrides are optional unless the template does not already define them.
  1. Supported actions
    1. Create the connection
    2. Create a rule
    3. Send a test event
    4. Review results
    5. Notes