# CleverTap integrations

> Call the CleverTap API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

CleverTap is a customer engagement and retention platform that tracks user profiles and app events, then sends targeted push, email, SMS and in-app campaigns. Tray.ai connects to CleverTap through the HTTP Connector, so your workflows can call the CleverTap API alongside the rest of your stack.

## Use cases

### User profiles

Read, create, and delete user profiles in CleverTap from any Tray.ai workflow. The CleverTap API covers calls such as get user profiles and upload user profiles.

- Get user profiles
- Upload user profiles
- Get profile count

### Events

Read and create events in CleverTap from any Tray.ai workflow. The CleverTap API covers calls such as get events and upload events.

- Get events
- Upload events
- Get event count

### Campaigns

Read and create campaigns in CleverTap from any Tray.ai workflow. The CleverTap API covers calls such as create a campaign and stop a scheduled campaign.

- Create a campaign
- Stop a scheduled campaign
- Get campaigns

### Catalog products

Read, create, update, and delete catalog products in CleverTap from any Tray.ai workflow. The CleverTap API covers calls such as list products and create a product.

- List products
- Create a product
- Update a product

### Content blocks

Read, create, and update content blocks in CleverTap from any Tray.ai workflow. The CleverTap API covers calls such as create a content block and list content blocks.

- Create a content block
- List content blocks
- Update a content block

### Reports

Read reports in CleverTap from any Tray.ai workflow. The CleverTap API covers calls such as get real-time counts and get message reports.

- Get real-time counts
- Get message reports
- Get trends

## Challenges Tray.ai solves

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

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

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

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

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