All Features

File Storage System: Tray Native File Storage

We’ve introduced the File System, a fully managed file storage layer within Tray. It allows you to upload and store files directly in the Tray platform, then access them in your automations using the File System connector.

This unlocks critical capabilities for building AI Agents and advanced automations that rely on handling unstructured data - such as PDFs, HTML pages, transcripts, or other documents - retrieved from external systems. Instead of sending data to third-party storage, you can now keep everything within Tray, simplifying architecture and reducing integration overhead.

What this enables:

• Store and retrieve files as part of your projects

• Build AI Agents that use file-based data sources (e.g. PDFs or transcripts for context)

• Parse, enrich, or summarize file contents using AI

Learn more in our File Storage System documentation.

Note: The File System feature is not supported in Embedded solutions.

Jump to Top / Bottom in Logs

We’ve added new navigation controls to the logs view: you can now jump straight to the top or bottom of a workflow execution with a single click. This makes it faster to navigate long or complex runs - especially useful for large workflows, looping executions, and detailed debugging.

Manual Error Handling Improvements

You now have more control over errors when choosing manual error handling. With this change, Tray will follow the failure paths for all errors without any automatic retries and backoffs. This now allows you to reference the error message allowing you to action errors in the manual handling path.

Your workflows will continue to use the existing error behaviours unless you explicitly disable it in the workflow settings. This gives you full control over when and where to adopt the new behaviours, without any risk of disruption to your current workflows.

For full information, including on how to enable this please visit our What is an Error documentation.

Create and Retrieve Namespace CDK Commands

You can now create and retrieve namespaces for your organisation using the following new commands introduced to the tray CDK. You no longer need to contact support desk before deploying your first CDK connector deployment to the platform.

To create a new namespace for your organisation:

$ tray-cdk namespace create ORGID NAMESPACE [--us] [--eu] [--ap]

To retrieve a namespace from your organisation:

$ tray-cdk namespace get ORGID [--us] [--eu] [--ap]

Where ORGID is the unique identifier of your organisation, which can be found in the tray app URL, for example https://app.tray.io/workspaces/ORGID

When creating a namespace we recommend:

• Associating with your company’s legal entity or brand name

• Choose a shorter name over a longer one

• Hyphens are supported, numbers and other symbols are not supported

• For example enter-company-name

New Variables in Alerting Workflows

We've expanded the available variables for alerting workflows. In the alerting trigger, you can now access:

• workspace_id

• workspace_name

• project_id

of the failing workflow. This makes it easier to identify where errors originate and improve error-handling processes.

Instantly Test Workflows with Mock Data

You can now easily test workflows that start with non-manual triggers - no more complicated workarounds.

Simply provide mock trigger output data and run the workflow immediately, just as if the real event had occurred.

To make this even easier, we’ve added Raw JSON input, allowing you to define test data freely - no UI restrictions. Use the Basic editor for structured input or switch to Raw JSON for full control.

This feature is currently available for a subset of non-manual triggers:

• Alert

• API Operation

• Callable

• Email

• Form

• Schedule

• Webhook

Optional Strict Mode for Schema Validation

We've introduced the ability to disable Strict Mode in API Operation triggers, offering more flexibility in handling JSON payloads. This enhancement allows fields not defined in the schema to flow through to your workflow instead of being filtered out.

SDLC: Custom Project Version Numbers

We've enhanced the Project Versioning functionality in our SDLC toolset to provide greater flexibility and control over version management. This update builds on the existing versioning capabilities by introducing the ability to save custom project version numbers, allowing you to align version numbers with your environment promotion processes or external systems.

What's new

• Custom Version Selection: Manually specify version numbers when saving a project version, breaking free from previous auto-incrementation constraints. Version numbers must still follow the major.minor numeric pattern.

• Consistent Versioning: Create new versions regardless of the previous version number (ensuring uniqueness), enabling better alignment with external systems and in multi-environment setups.