> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/using-the-history-tab-in-workflows.md).

# Using the History Tab in Workflows

Here's how to view and understand the History of your Workflows.

* Navigate to the **History** tab within the Workflow Builder.

{% embed url="<https://lh4.googleusercontent.com/m1m5jL8wOkm7cX-7uR-_9axKVD2guKLHsxj-6_FMZihmfrfSiPk4jTbx8HdN3UG2qbZdplbXwCBvyCFTfxM2xFQgSRanl6c3MaK5Eih-TChLSBjp6AOIX3ZZ2Dlm36xBMZ9LCP99YYJIHeq8JfbR5Q>" %}

* Use the dropdown menus to sort and filter through the list of contacts who’ve been through the Workflow.
* Here, you can view the Contacts, Action, Status, Executed On date, More Details, and Execution Log.
* For Contacts, you will be able to view the full history of actions for the contact within the specific workflow. If they’ve been in it more than once, you’ll see all the actions from each time they were added.
* Under More Details, you can view the details of the specific action.
* The Execution Log allows you to view the history of actions for the contact within the specific Workflow. If they’ve been in it more than once, you can use the icon to the left of their name for the complete history within this Workflow.


---

# 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://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/using-the-history-tab-in-workflows.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.