> For the complete documentation index, see [llms.txt](https://help.docexport.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docexport.com/getting-started/how-docexport-works.md).

# How DocExport works

DocExport turns the data on your monday.com board into finished documents — PDF or Word. Whatever you build, it always follows the **same simple flow**. Once that clicks, everything else in this help center falls into place.

{% hint style="info" %}
The whole app comes down to three beats: **Template → Generate → Download or (optional) Distribute.**
{% endhint %}

### The core flow

1. **a) Build a template** – a Microsoft Word (`.docx`) file where you mark, where your data should appear by using **placeholders.**\
   \
   **b) Use a predefined template** such as the Board or Item Print - DocExport provides several ready made templates that will give you your first result within seconds.
2. **Generate** – DocExport fills the template with real data from your board or item and shows a **live preview**.
3. **Download** – save the result as a **PDF** (or Word file).
4. **Distribute & automate** *(optional)* – send it by email, save it to a file column or have it generated automatically on a trigger (e.g. button click or status column change).

That flow is identical for every document, only the details inside each step change depending on the type you choose.

### The one choice that shapes everything: Item or Board

Before you build a template, decide what your document is about:

* **One item** (one client, one order, one task) → **Item Level**, using `{{Item.ColumnTitle}}` placeholders.
* **Many items as a table** (a report, a list) → **Board Level**, using Word merge tables.

This single choice determines which placeholders you use and how you generate. Walk through it here: [Item Level vs. Board Level](https://claude.ai/getting-started/item-level-vs-board-level.md).

### Placeholders: the glue

Placeholders are how your document knows which data to pull in. They sit in your Word file inside double curly braces and get replaced with real values when you generate:

`{{Item.Status}}` · `{{Due Date}}` · `{{User.name}}` · `{{Board.name}}`

Browse them all in the [Placeholder Directory](https://claude.ai/template/placeholder-directory.md).

{% hint style="success" %}
**First time?** When you open the DocExport view on a board, you'll be asked to **authorize the app** so it can read your board data. See [Authorize App](https://claude.ai/getting-started/authorize-app.md).
{% endhint %}

### Where to start

* **New to DocExport?** → [Item Level vs. Board Level](https://claude.ai/getting-started/item-level-vs-board-level.md), then follow [Item Level from A–Z](https://claude.ai/getting-started/item-level-from-a-z.md) or [Board Level from A–Z](https://claude.ai/getting-started/board-level-from-a-z.md).
* **Want a quick win?** → start from a ready-made design in the [Template Gallery](https://www.docexport.com/template-gallery/) and adapt it.
* **Only need an occasional one-click PDF for an item?** → [PDF Download in Item Card](https://claude.ai/getting-started/pdf-download-in-item-card.md).


---

# 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://help.docexport.com/getting-started/how-docexport-works.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.