# Campaign Cleaner integrations: campaigns

> Send a campaign, create an inbox test and add a domain in Campaign Cleaner. Connect Campaign Cleaner to the rest of your marketing stack with Tray.ai.

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

## Overview

Campaign Cleaner checks and repairs email campaign HTML before sending, fixing broken links, spam triggers, oversized images and client compatibility problems, and tests inbox placement. Tray.ai connects to Campaign Cleaner through the HTTP Connector, so your workflows can call the Campaign Cleaner API alongside the rest of your stack.

## Use cases

### Campaigns

Read, create, and delete campaigns in Campaign Cleaner from any Tray.ai workflow. The Campaign Cleaner API covers calls such as send a campaign and get campaign status.

- Send a campaign
- Get campaign status
- Get a campaign

### Inbox tests

Read and create inbox tests in Campaign Cleaner from any Tray.ai workflow. The Campaign Cleaner API covers calls such as create an inbox test and get inbox test results.

- Create an inbox test
- Get inbox test results

### Inbox placement monitor

Read and create inbox placement monitor in Campaign Cleaner from any Tray.ai workflow. The Campaign Cleaner API covers calls such as list monitored domains and add a domain.

- List monitored domains
- Add a domain
- List messages

### Account

Read account in Campaign Cleaner from any Tray.ai workflow. The Campaign Cleaner API covers calls such as get credits and get monitor usage.

- Get credits
- Get monitor usage

## Challenges Tray.ai solves

### Keeping Campaign Cleaner 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 Campaign Cleaner 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 Campaign Cleaner 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 Campaign Cleaner 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 Campaign Cleaner?

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

### How does Tray.ai authenticate with Campaign Cleaner?

The Campaign Cleaner 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 Campaign Cleaner connector?

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