# OutSystems integrations: applications

> Create an application version and publish an application across infrastructures in OutSystems.

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

## Overview

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.

## Use cases

### Applications

Read and create applications in OutSystems from any Tray.ai workflow. The OutSystems API covers calls such as create an application version and download source code.

- Create an application version
- Download source code
- Block an app from deployment

### Deployments

Work with deployments in OutSystems from any Tray.ai workflow. The OutSystems API covers calls such as deploy an application and publish an application across infrastructures.

- Deploy an application
- Publish an application across infrastructures
- Roll back a mobile app

### Environments

Work with environments in OutSystems from any Tray.ai workflow. The OutSystems API covers calls such as register an environment and unregister an environment.

- Register an environment
- Unregister an environment
- Map database connections

## Challenges Tray.ai solves

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

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

### 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.

### Can I get a dedicated OutSystems connector?

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