All Features

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.

SDLC API Suite

We have added new API endpoints to our Connectivity API suits, for all recently added SDLC features, including project version management, dependencies and deployment management. These new capabilities allow you to integrate deployment of Tray into existing CI/CD pipelines, eliminating the need for manual UI-based steps. This is especially beneficial for cross-region deployments and embedded use cases, where managing multiple organizations was previously a tedious process.

What this enables:

• Automate version management, including creating, listing, exporting, and importing project versions.

• Customize deployment pipelines instead of relying on fixed UI experience.

• Promote projects across environments, regions, and organizations programmatically.

• Validate import requirements and preview changes before committing deployments.

• Handle dependencies such as authentication and service mappings in an automated way.

For full information, please visit our Projects and Solutions APIs documentation.

Auto-Named Steps Based on Connector Operation

Steps are now automatically named based on their operation, giving you a clear, at-a-glance understanding of what each step does.Here’s what’s new:

• Instead of generic names like “Gmail” or “Text Helpers,” steps are now auto-named by their specific operations, e.g. "Send message", "Concatenate" or “List reports”.

• When you change the operation of a step, its name updates automatically to reflect the new operation - unless you’ve given it a custom name, which we preserve.

Workflows now essentially document themselves, making it easier to understand their functionality at a glance. This means less time spent naming steps and more time building powerful automations.

Building schemas from JSON

We’ve introduced a faster way to define and edit complex data structures in step properties, callables, config, and API schemas: Building schemas from JSON.

• Step Properties: Quickly generate objects and arrays by pasting JSON.

• Callable Workflows & APIM Schemas: Easily create input/output schemas with a JSON sample.

• Project Config: Edit your configuration directly with the new Raw JSON tab.

For more details, please see the feature's documentation.