2025

Changelog | May, 2025

Smart Labels for Node Input Variables

May 9th, 2025

Previously, Node input labels remained static regardless of their content. Now, input labels automatically update to reflect the value or expression they contain, making your Workflows more intuitive and self-documenting. You can set an explicit value at any time, at which point it will no longer auto-update.

Configurable Data Retention Policies

May 7th, 2025

Enterprise customers can now configure data retention policies for their organization. This new feature allows you to:

  • Set whether monitoring data is retained indefinitely (default) or for a specific time period
  • Choose from predefined retention periods (30, 60, 90, or 365 days)

Data retention settings can be configured from the Organization Settings page under Advanced Settings.

Data Retention Settings in Advanced Settings

Data Retention Settings in Advanced Settings

Data Retention Options

Data Retention Options

DeepSeek v3 to Azure AI Foundry

May 2nd, 2025

We now support the self-hosted DeepSeek v3 via Azure AI Foundry to Vellum.

GPT 4.1 and 4.5 Model via Azure OpenAI

May 2nd, 2025

We now support the self-hosted GPT 4.1 and GPT 4.5 models via Azure OpenAI to Vellum.

OpenAI Base64 PDF Files

May 2nd, 2025

We now support OpenAI Models newly added capability to use Base64 documents within API requests.

Structured Outputs and Json Mode Support for x AI Models

May 2nd, 2025

We have added the ability to have Grok models that are hosted on xAI to return responses in JSON format via an agnostic JSON Mode, or a formatted Structured Output.

Microsoft OmniParser V2 Azure AI Foundry

May 2nd, 2025

We’ve added support for Microsofts OmniParser V2 via Azure AI Foundry to Vellum

Gemini Vertex AI Models Are Now Region Specific

May 2nd, 2025

Previously, Gemini Vertex AI Models would be added to your account regionally agnostic. In the configuration of the model you would have to specify which region you would like to utilize the model in, therefore limiting you to one instance of the model.

We have pivoted to creating region specific instances for you to select. This allows you the option of enabling your model in different regions so you can set your workflows up for success with fallbacks to different regions.