All Features

Copy JSON path from logs

You can now right-click anywhere in the execution log output JSON to copy the full JSON path for that value. This is especially useful when working with complex objects and arrays. Once copied, the path can be used for direct data mapping, in interpolation strings, or for further processing in scripts.

Embedded Slots Usage

We’ve added a new way to track slot usage in your solutions: the Slots usage modal. You can now see exactly which workflows and steps each slot is used in. This makes it easier to manage dependencies, clean up unused slots, and understand the impact of any changes.

You’ll find the option under Slots usage in the dropdown next to the Publish draft button (next to Solution Settings).

Manual Error Handling Improvements

We’ve updated the default manual error handling behavior settings for new workflows.

What’s changed?

• Legacy Manual error handling is now disabled by default for newly created workflows. Please see your workflow settings to enable this.

• Existing workflows will continue using their current manual error behaviors unless you choose to update them in the workflow settings.

For details on how to configure error handling, visit our What is an Error documentation.

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.