# Dolibarr integrations: third parties and products

> Create a third party, create a product and create an order in Dolibarr, and start a workflow when Dolibarr sends “Third party created”.

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

## Overview

Dolibarr is a free, open-source ERP and CRM suite, self-hosted or cloud-hosted, where businesses switch on modules for customers, products, orders and invoicing. Tray.ai connects to Dolibarr through the HTTP Connector, so your workflows can call the Dolibarr API alongside the rest of your stack.

## Use cases

### Third parties

Read and create third parties in Dolibarr from any Tray.ai workflow. The Dolibarr API covers calls such as search third parties and create a third party.

- Search third parties
- Create a third party

### Products

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

- List products
- Create a product

### Orders

Create orders in Dolibarr from any Tray.ai workflow. The Dolibarr API covers calls such as create an order and add order lines.

- Create an order
- Add order lines
- Validate an order

## Challenges Tray.ai solves

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

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

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

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

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