# DocuWare integrations: file cabinets and documents

> Upload a document and add a text annotation in DocuWare. Connect DocuWare to the rest of your documents and e-signature stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/docuware-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

DocuWare is a document management and workflow system that stores business documents in indexed file cabinets and routes them through approval processes. Tray.ai connects to DocuWare through the HTTP Connector, so your workflows can call the DocuWare API alongside the rest of your stack.

## Use cases

### File cabinets

Read file cabinets in DocuWare from any Tray.ai workflow. The DocuWare API covers calls such as list file cabinets and get a file cabinet.

- List file cabinets
- Get a file cabinet
- List dialogs

### Documents

Read, create, update, and delete documents in DocuWare from any Tray.ai workflow. The DocuWare API covers calls such as search documents and get a document.

- Search documents
- Get a document
- Upload a document

### Annotations

Read, create, and delete annotations in DocuWare from any Tray.ai workflow. The DocuWare API covers calls such as get annotations and add a text annotation.

- Get annotations
- Add a text annotation
- Add a stamp

### Users

Read, create, and update users in DocuWare from any Tray.ai workflow. The DocuWare API covers calls such as list users and get a user.

- List users
- Get a user
- Create a user

### Workflows

Read workflows in DocuWare from any Tray.ai workflow. The DocuWare API covers calls such as get document workflow history and get workflow history steps.

- Get document workflow history
- Get workflow history steps

## Challenges Tray.ai solves

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

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

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

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

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