# EngageBay integrations: contacts and companies

> Create a contact, create a company and create a deal in EngageBay. Connect EngageBay to the rest of your sales stack with Tray.ai.

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

## Overview

EngageBay is a CRM for small businesses that combines contacts, deals, email marketing, tasks and help desk tickets in one account. Tray.ai connects to EngageBay through the HTTP Connector, so your workflows can call the EngageBay API alongside the rest of your stack.

## Use cases

### Contacts

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

- List contacts
- Create a contact
- Update a contact

### Companies

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

- List companies
- Create a company
- Update a company

### Deals

Read, create, update, and delete deals in EngageBay from any Tray.ai workflow. The EngageBay API covers calls such as list deals and create a deal.

- List deals
- Create a deal
- Update a deal

### Tasks

Read, create, update, and delete tasks in EngageBay from any Tray.ai workflow. The EngageBay API covers calls such as list tasks and create a task.

- List tasks
- Create a task
- Update a task

### Tickets

Read, create, and delete tickets in EngageBay from any Tray.ai workflow. The EngageBay API covers calls such as list tickets and create a ticket.

- List tickets
- Create a ticket
- Delete a ticket

### Products

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

- List products
- Create a product
- Update a product

## Challenges Tray.ai solves

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

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

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

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

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