Changelog | January, 2025

Prompt Node Cost and Model Name in Workflows

You can now see token cost and a model name in Prompt Node results when invoking a Workflow Deployment via API, by passing in True to the expand_meta.cost or the expand_meta.model_name parameter on either Execute Workflow endpoints.

1
stream = client.execute_workflow_stream(
2
  workflow_deployment_name="demo",
3
  inputs=[
4
    WorkflowRequestInputRequest_String(
5
      type="STRING",
6
      name="foo",
7
      value="bar",
8
    ),
9
  ],
10
  event_types=["WORKFLOW", "NODE"],
11
  expand_meta=WorkflowExpandMetaRequest(
12
    cost=True,
13
    model_name=True,
14
  )
15
)
16
17
for event in stream:
18
  if event.type == "NODE" and event.data.state == "FULFILLED":
19
    node_result_data = event.data.data
20
    if node_result_data and node_result_data.type == "PROMPT":
21
      print(node_result_data.data.execution_meta.cost)
22
      print(node_result_data.data.execution_meta.model_name)

Support for Gemini 2.0 Flash Thinking Mode

January 15th, 2025

We’ve added support for the Gemini 2.0 Flash Thinking Mode model.

Workflow Outputs Panel

January 10th, 2024

You’ll now see a new “Outputs” button that opens up the new “Workflows Outputs” panel in a Workflow Sandbox.

From here, you can see all the outputs that your Workflow produces, and easily navigate to the Nodes that produce them. In the coming weeks, you’ll also be able to directly edit your Workflow’s outputs from this panel.

Newly Added Support for DeepSeek Models

January 2nd, 2024

We’ve added support for DeepSeek AI models.

Along with the launch of the DeepSeek integration, we’ve added support for DeepSeek V3 Chat.

Function Call Inputs in Chat Messages

January 2nd, 2025

There is now first-class support for Function Call inputs to Chat Messages. This allows you to simulate the behavior of a Function Call output from a model in Vellum as part of a message in Chat History.

To see this feature in action, check out the video below: