# Lettr integrations: emails, campaigns and contacts

> Send an email, create a campaign and create a contact in Lettr, and start a workflow when Lettr sends “Email delivered”.

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

## Overview

Lettr is an email platform for developers that sends transactional emails and marketing campaigns, manages audience lists and templates, and tracks delivery and engagement. Tray.ai connects to Lettr through the HTTP Connector, so your workflows can call the Lettr API alongside the rest of your stack.

## Use cases

### Emails

Read, create, and delete emails in Lettr from any Tray.ai workflow. The Lettr API covers calls such as send an email and schedule an email.

- Send an email
- Schedule an email
- List email events

### Campaigns

Read and create campaigns in Lettr from any Tray.ai workflow. The Lettr API covers calls such as create a campaign and list campaigns.

- Create a campaign
- List campaigns
- Send a campaign now

### Contacts

Read, create, update, and manage contacts in Lettr from any Tray.ai workflow. The Lettr API covers calls such as list contacts and create a contact.

- List contacts
- Create a contact
- Bulk create contacts

### Audience lists

Read, create, update, and delete audience lists in Lettr from any Tray.ai workflow. The Lettr API covers calls such as list audience lists and create an audience list.

- List audience lists
- Create an audience list
- Update an audience list

### Templates

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

- List templates
- Create a template
- Update a template

### Domains

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

- List domains
- Create a domain
- Verify a domain

## Challenges Tray.ai solves

### Keeping Lettr 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 Lettr 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 Lettr 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 Lettr 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 Lettr?

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

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

The Lettr 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 Lettr connector?

Lettr runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Lettr connector from the Lettr 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/