# Bitrix24 integrations: deals, leads and contacts

> Create a deal, create a lead and create a contact in Bitrix24, and start a workflow when Bitrix24 sends “Deal created”.

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

## Overview

Bitrix24 is a business suite that combines a CRM with tasks, projects, chat, file storage, telephony and an online store for small and mid-sized teams. Tray.ai connects to Bitrix24 through the HTTP Connector, so your workflows can call the Bitrix24 API alongside the rest of your stack.

## Use cases

### Deals

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

- List deals
- Get a deal
- Create a deal

### Leads

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

- List leads
- Create a lead
- Update a lead

### Contacts

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

- List contacts
- Create a contact
- Update a contact

### Companies

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

- List companies
- Create a company

### Tasks

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

- List tasks
- Create a task
- Update a task

### Chat messages

Create and update chat messages in Bitrix24 from any Tray.ai workflow. The Bitrix24 API covers calls such as send a chat message and update a chat message.

- Send a chat message
- Update a chat message

## Challenges Tray.ai solves

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

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

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

The Bitrix24 API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Bitrix24 connector?

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