.DkNUKaKx_ZLAT4m.webp?dpl=dpl_Crv6NFYc4gRVqEEsmHdUK26mPGZB){kind=small}
Connectors / Documents and e-signature · HTTP Connector
Automate M-Files with Tray.ai
Create an object, upload a file and update object properties in M-Files. Connect M-Files to the rest of your documents and e-signature stack with Tray.ai.
Thanks — someone from our team will be in touch soon.
What can you do with M-Files on Tray.ai?
M-Files is a document management system that organizes files and records in vaults by metadata, with versioning, workflows and search. Tray.ai connects to M-Files through the HTTP Connector, so your workflows can call the M-Files API alongside the rest of your stack.
- Upload a file for each signed contract from your e-signature tool.
- Update object properties when the deal stage changes in your CRM.
- Create an object for each new supplier added in your ERP.
- Connects through
- HTTP Connector
- Authentication
- An API key in a request header or a bearer token
Set it up
Connect M-Files to Tray.ai
Each step uses M-Files's own API details, from its documentation.
Step 1
Save M-Files's API key
Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.
Step 2
Import a request from M-Files's docs
Add an HTTP Client step and paste a cURL example from M-Files's API docs. Tray.ai fills in the method, URL, headers, and query.
Step 3
Start with “List objects of a type”
It's one of 9 documented actions, under Objects. The response comes back as data the next step can map into your other apps.
Step 4
Hand it to an AI agent
Wrap “Create an object” and “Get an object version” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.
What the M-Files API covers
4 resources and 9 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.
Objects
- List objects of a type
- Create an object
- Get an object version
Files
- Upload a file
- Download file content
Views
- List view contents
- Search view contents
Properties
- Read object properties
- Update object properties
Checked against M-Files's own documentation on 2026-11-07
How Tray.ai makes this work
M-Files plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 9,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in M-Files — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose M-Files actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on M-Files data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More documents and e-signature apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every documents and e-signature connector →
Frequently asked questions
What can a Tray.ai workflow do in M-Files?
+
The M-Files API documents 9 actions across 4 resources (Objects, Files, Views, Properties). For example: List objects of a type; Upload a file; List view contents. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with M-Files?
+
The M-Files API uses an API key in a request header and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
See M-Files working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.