> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/integrations/noloco.md).
# Noloco
## Overview
This guide will walk you through the setup process for integrating [Noloco](https://noloco.io/) with Documint. It builds on the [Airtable Document Generation Link integration](/integrations/airtable/generation-link.md) so if you have not read the documentation on this integration, please check it out first before reading this guide.
### Airtable Setup
1. Create a generation link formula and add it to your table as a formula field. Also, add an attachment field to save your created document
### Noloco Setup
1. In Noloco, refresh your table structure
2. Navigate to the table that you added the generation link formula to
3. Enter Edit mode \
4. Enable generation link formula field and enter the field options edit mode. Check the following options: “Display as button”, “Open in a new tab” and add your own button text to the “Button text"\
\
5. Save your layout changes and exit edit mode
6. Test your button and review your document\
---
# 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.documint.me/integrations/noloco.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.