# ERPNext integrations

> Create a document in ERPNext and start a workflow when ERPNext sends “Document updated”. Connect ERPNext to the rest of your ERP stack with Tray.ai.

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

## Overview

ERPNext is open-source ERP software from Frappe covering accounting, inventory, sales, purchasing, manufacturing, and HR, run self-hosted or on Frappe Cloud. Tray.ai connects to ERPNext through the HTTP Connector, so your workflows can call the ERPNext API alongside the rest of your stack.

## Use cases

### Documents (any DocType, such as Customer or Sales Invoice)

Read, create, update, and delete documents (any doctype, such as customer or sales invoice) in ERPNext from any Tray.ai workflow. The ERPNext API covers calls such as list documents and create a document.

- List documents
- Create a document
- Read a document

### Whitelisted methods

Work with whitelisted methods in ERPNext from any Tray.ai workflow. The ERPNext API covers calls such as call a read-only method and call a method that changes data.

- Call a read-only method
- Call a method that changes data

## Challenges Tray.ai solves

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

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

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

The ERPNext API uses an API key in a request header, a bearer token, and 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 ERPNext connector?

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