> 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/introduction/use-case-library.md).

# Use Case Library

Learn how to build and generate documents with Documint through real, practical examples. Each use case walks you through a complete workflow — from connecting a data source to generating the final document — so you can see exactly how the pieces fit together for a specific scenario.

Every use case is available in two formats:

* **Video walkthrough** — watch the entire process from start to finish.
* **Step-by-step guide** — follow along with written instructions and screenshots at your own pace.

### What each use case covers

To keep things consistent, every use case in this library follows the same core workflow:

1. **Connect the blueprint to a data source** — link your template to the data that will populate it.
2. **Map fields** — match your data fields to the fields Documint will use.
3. **Add fields to the template** — place the mapped fields into your document design.
4. **Format fields** — control how values display (dates, currency, text styling, and more).
5. **Set up logic** — add conditionals, loops, or calculations to handle dynamic content.
6. **Generate the final document** — produce the finished, ready-to-use document.

### Browse by document type

{% content-ref url="/pages/5eBbSTno6JmevFEwKz7U" %}
[Invoices](/introduction/use-case-library/invoices.md)
{% endcontent-ref %}

### Generate documents by platform

Already have your data set up in one of Documint's integrations? These videos focus specifically on generating documents from that platform.

* Airtable
* HubSpot
* Make
* Zapier

### Don't see your use case?

If you're trying to build something that isn't covered here, reach out to our team — we're always adding new examples.


---

# 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/introduction/use-case-library.md?ask=<question>&goal=<user_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.