> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/actions/action-buttons/add-a-comment-action.md).
# Add a Comment Action
Add comments to a record through action buttons
You can add comments to a record through action buttons, enhancing app interactivity and automation. You can set this up in two ways: **One-Click Action Buttons** or **Modal Action Buttons**. Each setup enables users to add either fixed or custom comments directly to a record.
### **One-Click Action Buttons**
1. **Choose Action**: Select **Add a Comment**.
2. **Choose a Type**: Choose if this should be recorded as a **comment** or a **note**.
3. **Define Fixed Text**: Enter the text to be automatically added to the record. You can use dynamic tokens (e.g., {{user.name}}), but users won’t be able to edit it before submission.
### **Modal Action Buttons**
1. **Choose Action**: Select **Add a Comment**.
2. **Choose a Type**: Decide if this will be a **comment** or a **note**.
3. The user will be prompted with a text input box to add their comment. They can format text, upload files, and modify the comment before submission.
---
# 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://guides.noloco.io/actions/action-buttons/add-a-comment-action.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.
