Set Run Title
The Set Run Title block assigns a title to the current agent run, which appears in the user's run history.
Set a custom title for the current agent run
The Set Run Title block assigns a title to the current agent run, which appears in the user's run history. It takes a single text input — the title string — and applies it as a label to the active run session. This makes it straightforward to give each run a meaningful, human-readable name rather than relying on a default or auto-generated identifier.
The block accepts one configurable field: a title string defined in the setRunTitle configuration object. This value can be static text or dynamically constructed using variables from earlier steps in the workflow, allowing the title to reflect context such as user input, a topic, a date, or any other relevant data available at runtime.
This block fits into workflows where run history clarity matters — for example, applications that handle multiple distinct tasks per user, support workflows that process different case types, or any workflow where users or administrators need to distinguish between past runs at a glance. It produces no output of its own, functioning purely as a labeling step within the workflow sequence.
What you can build
Real-world workflows powered by the Set Run Title block.
Label Customer Support Cases
Set the run title to the customer's name or issue type so support agents can quickly identify past interactions in run history.
Track Document Processing Jobs
Assign the document filename or type as the run title when processing uploaded files, making each run identifiable in history.
Name Research Sessions
Use the user's research topic or query as the run title so users can return to specific research sessions from their history.
Identify Scheduled Report Runs
Set a title combining the report name and date for automated reporting workflows, enabling easy auditing of past report generations.
Distinguish Multi-User Workflows
Incorporate the user's name or ID into the run title so administrators can filter and review individual user sessions in history.
Tag Onboarding Flow Instances
Label each onboarding run with the new user's name or account type to keep a clear record of completed onboarding sessions.
Ready to add Set Run Title to your workflow?
Get Started FreeCommon questions about Set Run Title
What is the required parameter for this block?
The block requires a single parameter: a title string, configured in the setRunTitle object under the key 'title'. This is the text that will be assigned as the label for the current agent run.
What does this block return as output?
The Set Run Title block produces no output. It performs a labeling action on the current run session and does not pass any data to subsequent blocks.
Can the title be set dynamically using variables?
The title field accepts a string value, which can be constructed using variables or data from earlier steps in the workflow, allowing the run title to reflect dynamic context such as user input or computed values.
Where does the run title appear after it is set?
According to the block description, the title appears in the user's run history, providing a human-readable label for that specific agent run session.
What kinds of workflows commonly use this block?
This block is commonly used in workflows where multiple distinct runs need to be differentiated in history — such as support ticket handling, document processing, research assistants, or any multi-session application where users or administrators review past runs.
Related capabilities
Start
Specifies how the workflow is invoked
User Input
Prompt the user for one or more pieces of data that will be saved as a variable. Can include text, multiple choice, images, or files.
Run Function
Execute a custom JavaScript or Python function
Chat
Start a chat session with an LLM.
End
End the workflow. Optionally return a structured output (for API) or send notifications.
Jump
Transition to another workflow, maintaining the same scope
Add Set Run Title to your workflow
Build powerful AI workflows with drag-and-drop blocks. No coding required.