Skip to content
Mendix logo

Connectors / Developer tools · HTTP Connector

Automate Mendix with Tray.ai

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

What can you do with Mendix on Tray.ai?

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.

  • When Mendix sends “Alert triggered”, page the on-call engineer through your incident tool.
  • Post the build details to the release team's chat channel when Mendix sends “Package uploaded”.
  • Transport a package to an environment once the change is approved in your release tracker.
  • Download app logs after an incident and attach them to the ticket in your issue tracker.
Connects through
HTTP Connector
Authentication
An API key in a request header

Set it up

Connect Mendix to Tray.ai

Each step uses Mendix's own API details, from its documentation.

Step 1

Save Mendix'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 Mendix's docs

Add an HTTP Client step and paste a cURL example from Mendix's API docs. Tray.ai fills in the method, URL, headers, and query.

Step 3

Start with “List apps”

It's one of 15 documented actions, under Apps. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Mendix events

Give Mendix the URL of a Tray.ai webhook trigger. “Package uploaded” can then start a workflow, and so can 2 other events.

Workflows to build with Mendix

Each one uses actions and events from Mendix's own API documentation.

Alert the team in Slack when a Mendix alert fires

When

Alert triggered

Then

  1. Download app logs for the affected environment
  2. Post the alert and log link to the ops channel in Slack

With Slack

Deploy approved Mendix packages to an environment

When

Package uploaded

Then

  1. Create a change request in ServiceNow
  2. When approved, transport a package to an environment
  3. Update the change request with the result

With ServiceNow

Open a Jira incident for Mendix alerts

When

Alert triggered

Then

  1. Create an issue in Jira with the alert details
  2. Download access logs and attach them to the issue

With Jira

Apps you can build on Mendix data

Internal tools your team can build with an AI assistant, each one using Mendix calls from its API documentation.

Environment status board

Lists apps and their environments and lets an admin start or stop an environment.

Release transport request

Shows newly uploaded packages and lets a release lead transport a package to the chosen environment.

Environment alert feed

Collects triggered alerts next to environment tags so on-call staff can see which apps need attention.

Give your AI agents Mendix tools

Build an MCP server on Mendix in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works

  • List apps
  • List environments
  • Upload a package
  • Create environment tags
  • Download app logs
  • Get an app
  • Start an environment
  • Stop an environment

What the Mendix API covers

5 resources and 15 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.

Apps

  • List apps
  • Get an app

Environments

  • List environments
  • Start an environment
  • Stop an environment
  • Scale an environment
  • Update environment settings

Deployment packages

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

Environment tags

  • Create environment tags
  • List environment tags
  • Delete environment tags

Logs

  • Download app logs
  • Download access logs

Events Mendix can send to a Tray.ai webhook trigger

  • Package uploaded
  • Team Server push
  • Alert triggered

Checked against Mendix's own documentation on 2026-10-22

docs.mendix.com/apidocs-mxsdk/apidocs/deploy-api

Frequently asked questions

What can a Tray.ai workflow do in Mendix?

+

The Mendix API documents 15 actions across 5 resources (Apps, Environments, Deployment packages, Environment tags, Logs). For example: List apps; List environments; Upload a package. A workflow can make any documented call through the HTTP Connector.

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.

Which Mendix events can start a Tray.ai workflow?

+

Mendix sends 3 events to a webhook URL, for example: Package uploaded; Team Server push; Alert triggered. A Tray.ai webhook trigger receives them and starts a workflow.

See Mendix working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.