# Emelia integrations: campaigns

> Create a campaign, add a contact to a campaign and create a list in Emelia, and start a workflow when Emelia sends “Email sent”.

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

## Overview

Emelia is a B2B prospecting tool that runs cold email, LinkedIn, and WhatsApp outreach campaigns, finds and verifies contact details, and gathers replies in one inbox. Tray.ai connects to Emelia through the HTTP Connector, so your workflows can call the Emelia API alongside the rest of your stack.

## Use cases

### Campaigns

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

- List campaigns
- Create a campaign
- Get a campaign

### Campaign contacts

Read, create, and delete campaign contacts in Emelia from any Tray.ai workflow. The Emelia API covers calls such as list campaign contacts and add a contact to a campaign.

- List campaign contacts
- Add a contact to a campaign
- Remove a contact from a campaign

### Lists

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

- List your lists
- Create a list
- Rename a list

### List contacts

Create, update, and delete list contacts in Emelia from any Tray.ai workflow. The Emelia API covers calls such as add a contact to a list and add contacts in bulk.

- Add a contact to a list
- Add contacts in bulk
- Update a contact

### Email Finder

Read email finder in Emelia from any Tray.ai workflow. The Emelia API covers calls such as find a person's email and get an email search result.

- Find a person's email
- Get an email search result

### Phone Finder

Read phone finder in Emelia from any Tray.ai workflow. The Emelia API covers calls such as find a person's phone number and get a phone search result.

- Find a person's phone number
- Get a phone search result

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Emelia connector?

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