# Kustomer integrations: customers and conversations

> Create a customer, create a conversation and create a message in Kustomer, and start a workflow when Kustomer sends “Conversation created”.

**Canonical page:** https://tray.ai/connectors/kustomer-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

Kustomer is a customer service platform that keeps each customer's full history in one timeline, so support agents can answer email, chat, SMS and social conversations in one place. Tray.ai connects to Kustomer through the HTTP Connector, so your workflows can call the Kustomer API alongside the rest of your stack.

## Use cases

### Customers

Read, create, update, and delete customers in Kustomer from any Tray.ai workflow. The Kustomer API covers calls such as list customers and get a customer.

- List customers
- Get a customer
- Create a customer

### Conversations

Read, create, and update conversations in Kustomer from any Tray.ai workflow. The Kustomer API covers calls such as list conversations and get a conversation.

- List conversations
- Get a conversation
- Create a conversation

### Messages

Read, create, and update messages in Kustomer from any Tray.ai workflow. The Kustomer API covers calls such as list messages and get a message.

- List messages
- Get a message
- Create a message

### Companies

Read, create, and update companies in Kustomer from any Tray.ai workflow. The Kustomer API covers calls such as list companies and get a company.

- List companies
- Get a company
- Create a company

### Notes

Read, create, update, and delete notes in Kustomer from any Tray.ai workflow. The Kustomer API covers calls such as list notes and create a note.

- List notes
- Create a note
- Update a note

### Custom objects

Read, create, update, and delete custom objects in Kustomer from any Tray.ai workflow. The Kustomer API covers calls such as list custom objects and create a custom object.

- List custom objects
- Create a custom object
- Update a custom object

## Challenges Tray.ai solves

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

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

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

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

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