# echowin integrations: agents and knowledge bases

> Update agent instructions, create a Q&A reference and create a contact in echowin. Connect echowin to the rest of your AI stack with Tray.ai.

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

## Overview

echowin is a platform for building AI phone and chat agents that answer calls, chats, and messages for a business, with contacts, knowledge bases, and call logs. Tray.ai connects to echowin through the HTTP Connector, so your workflows can call the echowin API alongside the rest of your stack.

## Use cases

### Agents

Read and update agents in echowin from any Tray.ai workflow. The echowin API covers calls such as list agents and get agent instructions.

- List agents
- Get agent instructions
- Update agent instructions

### Knowledge bases

Read, create, update, and manage knowledge bases in echowin from any Tray.ai workflow. The echowin API covers calls such as get a knowledge base and search a knowledge base.

- Get a knowledge base
- Search a knowledge base
- Create a Q&A reference

### Contacts

Read, create, update, and delete contacts in echowin from any Tray.ai workflow. The echowin API covers calls such as list contacts and get a contact.

- List contacts
- Get a contact
- Create a contact

### Calls

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

- List calls
- Get a call

### Chats

Read chats in echowin from any Tray.ai workflow. The echowin API covers calls such as list chat conversations and get a chat conversation.

- List chat conversations
- Get a chat conversation

### Tags

Read and create tags in echowin from any Tray.ai workflow. The echowin API covers calls such as list tags and create a tag.

- List tags
- Create a tag

## Challenges Tray.ai solves

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

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

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

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

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