> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/automation/flow-builder/dynamic-title.md).

# Dynamic Title

Adding dynamic data to step titles

Sometimes it quite difficult to find specific steps in the Flow Debugger because e.g. the ID one is searching for is not part of the step’s title or endpoint and thus the step can't easily be found.

With the **Dynamic Title Postfix** field you can now add dynamic data to step titles, which will be fully searchable in the Flow Debugger:

<figure><img src="https://291121471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McrRFZHYH27bqKzOVDd%2Fuploads%2Fz3KBtxGIhFwVfCfSQJQF%2Fimage.png?alt=media&amp;token=170439be-aa08-4ae9-808e-51ffe6da38dd" alt=""><figcaption><p>Edit dialog will be visible when clicking on <strong>Edit</strong> in the action sidebar</p></figcaption></figure>

There you could for example add the external id of a record you are updating or even add the main record id of a current loop iterations to all steps of the Loop.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.locoia.com/automation/flow-builder/dynamic-title.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.