# Callingly integrations: calls, leads and SMS

> Create a call, update a lead and send an SMS in Callingly, and start a workflow when Callingly sends “Call completed”.

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

## Overview

Callingly is speed-to-lead software that calls and texts new leads within seconds and connects them to the right sales rep. Tray.ai connects to Callingly through the HTTP Connector, so your workflows can call the Callingly API alongside the rest of your stack.

## Use cases

### Calls

Read and create calls in Callingly from any Tray.ai workflow. The Callingly API covers calls such as list calls and get a call.

- List calls
- Get a call
- Create a call

### Leads

Read, update, and delete leads in Callingly from any Tray.ai workflow. The Callingly API covers calls such as list leads and get a lead.

- List leads
- Get a lead
- Update a lead

### SMS

Read and create sms in Callingly from any Tray.ai workflow. The Callingly API covers calls such as send an SMS and schedule an SMS.

- Send an SMS
- Schedule an SMS
- List SMS messages

### Teams

Read, create, and update teams in Callingly from any Tray.ai workflow. The Callingly API covers calls such as list teams and create a team.

- List teams
- Create a team
- Update a team

### Agents

Read, create, update, and delete agents in Callingly from any Tray.ai workflow. The Callingly API covers calls such as list agents and create an agent.

- List agents
- Create an agent
- Update an agent

### Callingly events

Start a Tray.ai workflow the moment something happens in Callingly. Callingly sends events such as call completed and lead created to a Tray.ai webhook trigger.

- Call completed
- Lead created
- Lead updated

## Challenges Tray.ai solves

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

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

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

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

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