Sending Emails

Overview

Send emails to your audience using campaigns. Campaigns let you select a segment or list as recipients, configure sender settings, and track results.

Email logs and tracking — Real-time delivery logs with open, click, and bounce tracking

Email sending in Migma is done through the Campaigns section, not from the Contacts page directly.

Quick Start

Create your email

Use Migma’s AI tools to create an email in the chat editor.

Set up your audience

Add contacts, organize with lists, and create segments from the Audience page.

Create a campaign

Go to Campaigns and create a campaign. Select your email, choose recipients (segment or list), configure sender settings, and send or schedule.

Prerequisites

Email service provider required — configure an ESP before sending.

Connected email provider (Migma, Amazon SES, Resend, SendGrid, or Mailgun)
Verified sending domain
At least one contact with subscribed status

Setup Email Provider

Connect and configure your email service provider

Unsubscribe & Compliance

Migma handles compliance automatically:

Unsubscribe links are added to every marketing email
Clicking unsubscribe updates the contact’s status immediately
Unsubscribed contacts cannot receive marketing emails
Preference center lets subscribers manage their topic preferences

Send via API

Send emails programmatically via the SDK, CLI, or API. The from address determines your sending domain — it must be a verified domain. The optional providerType field selects which email service provider delivers the message. It defaults to migma (built-in sending). For generated emails, use the emailId returned by generation status or shown in Publish → Send via API. conversationId identifies the whole chat thread; it works for single-email conversations, but multi-slot emails and series need emailId so the API knows which email to send.

await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourcompany.migma.email',
  fromName: 'Your Company',
  subject: 'Welcome!',
  emailId: 'email_123'
});

Migma (default)
Amazon SES
Resend
SendGrid
Mailgun

No providerType needed — Migma sends by default. Use a verified sending domain (managed or custom).

await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourcompany.migma.email',
  fromName: 'Your Company',
  subject: 'Welcome!',
  template: source,
  projectId: 'proj_123'
});

Requires Amazon SES connected in Settings → Integrations.

await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourdomain.com',
  fromName: 'Your Company',
  subject: 'Welcome!',
  template: source,
  projectId: 'proj_123',
  providerType: 'ses'
});

Requires Resend connected in Settings → Integrations.

await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourdomain.com',
  fromName: 'Your Company',
  subject: 'Welcome!',
  template: source,
  projectId: 'proj_123',
  providerType: 'resend'
});

Requires SendGrid connected in Settings → Integrations.

await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourdomain.com',
  fromName: 'Your Company',
  subject: 'Welcome!',
  template: source,
  projectId: 'proj_123',
  providerType: 'sendgrid'
});

Requires Mailgun connected in Settings → Integrations.

await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'sarah@example.com',
  from: 'hello@yourdomain.com',
  fromName: 'Your Company',
  subject: 'Welcome!',
  template: source,
  projectId: 'proj_123',
  providerType: 'mailgun'
});

Sending Domains

Set up and verify a sending domain

Email Service Providers

Connect an external ESP

Transactional vs Marketing

Migma automatically infers the email type from how you send:

Send type	Default behavior	Example
Single recipient (`recipientType: 'email'`)	Transactional	Order confirmations, password resets
Batch (`recipientType: 'audience'`, `'tag'`)	Marketing	Newsletters, promotions

Transactional emails bypass subscription status, skip topic filtering, and omit List-Unsubscribe headers. Bounced addresses are always excluded. This means single sends just work — no extra flags needed:

// Automatically treated as transactional — no flag needed
await migma.sending.send({
  recipientType: 'email',
  recipientEmail: 'customer@example.com',
  from: 'noreply@yourcompany.migma.email',
  fromName: 'Your Company',
  subject: 'Your order has shipped',
  template: source,
  projectId: 'proj_123'
});

For edge cases, use the transactional flag to override the default:

// Batch transactional: "Your subscription renews tomorrow" to all active users
await migma.sending.send({
  recipientType: 'tag',
  recipientId: 'tag_active_subscribers',
  from: 'noreply@yourcompany.migma.email',
  fromName: 'Your Company',
  subject: 'Your subscription renews tomorrow',
  template: source,
  projectId: 'proj_123',
  transactional: true
});

Only use transactional: true on batch sends for emails the recipient expects regardless of subscription status (renewal reminders, security alerts). Using it for promotional content violates CAN-SPAM and GDPR.

Next Steps

Send a Campaign

Step-by-step campaign guide

Track Results

Monitor campaign performance

Manage Contacts

Organize your subscriber list

Setup ESP

Connect email service provider

Getting Started

Create

Import & Remix

Review & Export

Campaigns

Audience

Sending Domains

Workspace & Settings

Deliverability

Resources

Comparisons

Referral & Company

Overview

Quick Start

Prerequisites

Setup Email Provider

Unsubscribe & Compliance

Send via API

Sending Domains

Email Service Providers

Transactional vs Marketing

Next Steps

Send a Campaign

Track Results

Manage Contacts

Setup ESP

​Overview

​Quick Start

​Prerequisites

Setup Email Provider

​Unsubscribe & Compliance

​Send via API

Sending Domains

Email Service Providers

​Transactional vs Marketing

​Next Steps

Send a Campaign

Track Results

Manage Contacts

Setup ESP

Overview

Quick Start

Prerequisites

Unsubscribe & Compliance

Send via API

Transactional vs Marketing

Next Steps