# Mendix integrations: apps and environments

> Start an environment, upload a package and create environment tags in Mendix, and start a workflow when Mendix sends “Package uploaded”.

**Canonical page:** https://tray.ai/connectors/mendix-integrations/
**Categories:** Developer tools
**Connects through:** HTTP Connector

## Overview

Mendix is a low-code platform for building and running business apps, with Mendix Cloud hosting the environments those apps are deployed to. Tray.ai connects to Mendix through the HTTP Connector, so your workflows can call the Mendix API alongside the rest of your stack.

## Use cases

### Apps

Read apps in Mendix from any Tray.ai workflow. The Mendix API covers calls such as list apps and get an app.

- List apps
- Get an app

### Environments

Read, create, and update environments in Mendix from any Tray.ai workflow. The Mendix API covers calls such as list environments and start an environment.

- List environments
- Start an environment
- Stop an environment

### Deployment packages

Read and create deployment packages in Mendix from any Tray.ai workflow. The Mendix API covers calls such as upload a package and transport a package to an environment.

- Upload a package
- Transport a package to an environment
- Get the environment package

### Environment tags

Read, create, and delete environment tags in Mendix from any Tray.ai workflow. The Mendix API covers calls such as create environment tags and list environment tags.

- Create environment tags
- List environment tags
- Delete environment tags

### Logs

Read logs in Mendix from any Tray.ai workflow. The Mendix API covers calls such as download app logs and download access logs.

- Download app logs
- Download access logs

### Mendix events

Start a Tray.ai workflow the moment something happens in Mendix. Mendix sends events such as package uploaded and team Server push to a Tray.ai webhook trigger.

- Package uploaded
- Team Server push
- Alert triggered

## Challenges Tray.ai solves

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

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

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

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

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