MailerSend

Use the MailerSend connector when your team already sends transactional mail through MailerSend and wants GenieOS to own authoring, approvals, schemas, and send audit trails.

Before you start

• Create a MailerSend API token with email sending permissions.
• Verify the sending domain in MailerSend.

Setup

sequenceDiagram
  participant Admin as Workspace admin
  participant MG as GenieOS
  participant MS as MailerSend
  participant User as Recipient

  Admin->>MS: Create API token
  Admin->>MG: Install MailerSend connector
  MG->>MS: Test token and sending domain
  MG->>MS: Register activity webhook
  MG->>MS: Send message via API
  MS->>User: Deliver email
  MS->>MG: Delivery webhook events

1. Open Settings → Connectors and choose MailerSend.
2. Paste the MailerSend API token.
3. Pick the sending domain and default sender details.
4. Finish install. GenieOS registers the activity webhook with MailerSend automatically — you do not paste a URL or signing secret into MailerSend. MailerSend generates the secret; we store it.
5. Send a connector test.

Capabilities

Webhooks and suppressions

GenieOS registers the webhook via MailerSend's API when you pick a sending domain at install. You do not create the webhook or paste a signing secret in the MailerSend dashboard — MailerSend generates the secret and we store it.

If automatic registration did not complete (for example you skipped the domain step), add the endpoint shown on the connector page under MailerSend → Domains → your domain → Webhooks. Enable delivery, bounce, complaint, open, click, and unsubscribe events if they are available on your MailerSend plan.

Troubleshooting

• 401 or 403 during testing usually means the API token is missing required scopes or belongs to the wrong MailerSend workspace.
• Domain errors usually mean the from address does not match a verified MailerSend domain.
• Missing opens and clicks often mean tracking is disabled in MailerSend.