.DkNUKaKx_ZLAT4m.webp?dpl=dpl_2g7utNqo1QcVopVsXyXRGLPAkqY1){kind=small}
Connectors / Developer tools · HTTP Connector
Automate OutSystems with Tray.ai
Create an application version and publish an application across infrastructures in OutSystems.
What can you do with OutSystems on Tray.ai?
OutSystems is a low-code platform for building and running business applications, with LifeTime as the console that manages environments, teams and deployments. Tray.ai connects to OutSystems through the HTTP Connector, so your workflows can call the OutSystems API alongside the rest of your stack.
- Deploy an application with OutSystems when a release is approved in your change management tool.
- Block an app from deployment in OutSystems when a security scan finds a critical issue.
- Create an application version in OutSystems when a release ticket moves to ready in your issue tracker.
- Download source code from OutSystems after each release and store it in your backup storage.
- Connects through
- HTTP Connector
- Authentication
- A bearer token
- Base URL
- https://{lifetime-domain}/lifetimeapi/rest/v2
Set it up
Connect OutSystems to Tray.ai
Each step uses OutSystems's own API details, from its documentation.
Step 1
Save OutSystems's API token
Save the token OutSystems issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://{lifetime-domain}/lifetimeapi/rest/v2 as the base URL. Or paste a cURL example from OutSystems's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “Create an application version”
It's one of 9 documented actions, under Applications. The response comes back as data the next step can map into your other apps.
Step 4
Hand it to an AI agent
Wrap “Download source code” and “Deploy an application” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.
Give your AI agents OutSystems tools
Build an MCP server on OutSystems 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
- Create an application version
- Deploy an application
- Register an environment
- Download source code
- Block an app from deployment
- Publish an application across infrastructures
- Roll back a mobile app
- Unregister an environment
What the OutSystems API covers
3 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.
Applications
- Create an application version
- Download source code
- Block an app from deployment
Deployments
- Deploy an application
- Publish an application across infrastructures
- Roll back a mobile app
Environments
- Register an environment
- Unregister an environment
- Map database connections
Checked against OutSystems's own documentation on 2026-10-22
How Tray.ai makes this work
OutSystems plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 10,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 OutSystems — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose OutSystems actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on OutSystems data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More developer tools apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every developer tools connector →
Frequently asked questions
What can a Tray.ai workflow do in OutSystems?
+
The OutSystems API documents 9 actions across 3 resources (Applications, Deployments, Environments). For example: Create an application version; Deploy an application; Register an environment. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with OutSystems?
+
The OutSystems API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
See OutSystems 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.