# Unisender integrations: lists and contacts

> Create a list, import contacts and create an email message in Unisender, and start a workflow when Unisender sends “Email status changed”.

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

## Overview

Unisender is an email and SMS marketing service for building contact lists, sending campaigns and transactional messages, and tracking delivery statistics. Tray.ai connects to Unisender through the HTTP Connector, so your workflows can call the Unisender API alongside the rest of your stack.

## Use cases

### Lists

Read, create, update, and delete lists in Unisender from any Tray.ai workflow. The Unisender API covers calls such as list contact lists and create a list.

- List contact lists
- Create a list
- Update a list

### Contacts

Read and create contacts in Unisender from any Tray.ai workflow. The Unisender API covers calls such as subscribe a contact and unsubscribe a contact.

- Subscribe a contact
- Unsubscribe a contact
- Import contacts

### Messages

Create messages in Unisender from any Tray.ai workflow. The Unisender API covers calls such as create an email message and create an SMS message.

- Create an email message
- Create an SMS message
- Send an email

### Campaigns

Read, create, and delete campaigns in Unisender from any Tray.ai workflow. The Unisender API covers calls such as create a campaign and cancel a campaign.

- Create a campaign
- Cancel a campaign
- Get campaign status

### Templates

Read, create, update, and delete templates in Unisender from any Tray.ai workflow. The Unisender API covers calls such as create an email template and update an email template.

- Create an email template
- Update an email template
- Delete a template

### Fields and tags

Read, create, and delete fields and tags in Unisender from any Tray.ai workflow. The Unisender API covers calls such as list fields and create a field.

- List fields
- Create a field
- Delete a field

## Challenges Tray.ai solves

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

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

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

The Unisender API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Unisender connector?

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