# Kixie integrations: calls and text messages

> Send a contact to a queue, send an SMS and add to a PowerList in Kixie, and start a workflow when Kixie sends “Dial attempt”.

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

## Overview

Kixie is a cloud phone and texting system for sales teams, with a power dialer, call queues, cadences and CRM-linked call logging. Tray.ai connects to Kixie through the HTTP Connector, so your workflows can call the Kixie API alongside the rest of your stack.

## Use cases

### Calls

Create and delete calls in Kixie from any Tray.ai workflow. The Kixie API covers calls such as make a call and send a contact to a queue.

- Make a call
- Send a contact to a queue
- Remove a contact from a queue

### Text messages

Create text messages in Kixie from any Tray.ai workflow. The Kixie API covers calls such as send an SMS and send a team SMS.

- Send an SMS
- Send a team SMS

### PowerLists

Create and delete powerlists in Kixie from any Tray.ai workflow. The Kixie API covers calls such as add to a PowerList and remove from a PowerList.

- Add to a PowerList
- Remove from a PowerList
- Remove from all PowerLists

### Cadences

Create and delete cadences in Kixie from any Tray.ai workflow. The Kixie API covers calls such as send to a cadence and remove from a cadence.

- Send to a cadence
- Remove from a cadence

### Kixie events

Start a Tray.ai workflow the moment something happens in Kixie. Kixie sends events such as dial attempt and call started to a Tray.ai webhook trigger.

- Dial attempt
- Call started
- Call answered

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Kixie connector?

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