> 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

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="/files/wtBrVXWX8rckLkEoDK1p" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
