> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/tools/activity-log.md). # Activity Log The **Activity Log** tool allows you to log information about your workflow when it runs. This can be used to help debug issues with your setup. Fields included in the Activity Log are: * **Activity Message:** Label the data that you'd like to log so that you can easily recognize the Activity Log's logging. Example: Order Data. * **Payload Value:** Add [Variables](/workflow-builder/fields/variables.md) that you'd like to view the data of. You are allowed to add multiple variables and characters.
Screenshot of the MESA Activity Log tool step showing the Activity Message and Payload Value fields used to log workflow data. Spotlight the Activity Message and Payload Value fields.
Logs created from this step can be found in your workflow's **Logs** tab. Here is an example of the logged information specified in a workflow and where you can see additional details in the logs.
Screenshot of the MESA Logs tab showing the logged Activity Log information from a workflow run with additional details. Spotlight the Activity Log entry in the Logs tab.
--- # 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.getmesa.com/tools/activity-log.md?ask=&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.