# MailerSend integrations: email and templates

> Send an email, create a template and add a domain in MailerSend, and start a workflow when MailerSend sends “Email sent”.

**Canonical page:** https://tray.ai/connectors/mailersend-integrations/
**Categories:** Communication
**Connects through:** HTTP Connector

## Overview

MailerSend is a transactional email and SMS service for developers, covering sending, templates, domain setup, delivery tracking and inbound routing. Tray.ai connects to MailerSend through the HTTP Connector, so your workflows can call the MailerSend API alongside the rest of your stack.

## Use cases

### Email

Read and create email in MailerSend from any Tray.ai workflow. The MailerSend API covers calls such as send an email and send bulk emails.

- Send an email
- Send bulk emails
- Get bulk email status

### Templates

Read, create, update, and delete templates in MailerSend from any Tray.ai workflow. The MailerSend API covers calls such as list templates and get a template.

- List templates
- Get a template
- Create a template

### Domains

Read, create, and delete domains in MailerSend from any Tray.ai workflow. The MailerSend API covers calls such as list domains and get a domain.

- List domains
- Get a domain
- Add a domain

### Recipients

Read and delete recipients in MailerSend from any Tray.ai workflow. The MailerSend API covers calls such as list recipients and get a recipient.

- List recipients
- Get a recipient
- Delete a recipient

### Webhooks

Read, create, update, and delete webhooks in MailerSend from any Tray.ai workflow. The MailerSend API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

### MailerSend events

Start a Tray.ai workflow the moment something happens in MailerSend. MailerSend sends events such as email sent and email delivered to a Tray.ai webhook trigger.

- Email sent
- Email delivered
- Email soft bounced

## Challenges Tray.ai solves

### Keeping MailerSend credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store MailerSend credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the MailerSend API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the MailerSend API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to MailerSend?

Yes. Tray.ai connects to MailerSend through the HTTP Connector, which calls the MailerSend API directly. Any call the MailerSend API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with MailerSend?

The MailerSend API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated MailerSend connector?

MailerSend runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated MailerSend connector from the MailerSend API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/