> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/convert-to-pdf-and-merge.md).

# Convert to PDF and merge documents

Use this flow action to convert or merge documents

## Action name: "Convert to PDF"

This flow action converts a document to PDF, and also lets you merge several documents into a single one.

**In a Salesforce flow:**

### Add the Convert to PDF action

* **Content Version ID**: Enter the ID of the Content Version to convert to PDF, or to which you want to add documents as appendices\
  You can retrieve this value with a Get Records element in the flow.

If you want to merge several documents, create a collection variable to store the appendices

* **Annexes IDS**: Enter the collection variable in which you stored the IDs of the documents to add to the main document.\
  Content Version IDs are expected here\
  You can retrieve the documents through a screen or with a Get Records element in the flow, for example

{% hint style="warning" %}
**Tip**

An example flow is available in the pre-built Flow Org
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/convert-to-pdf-and-merge.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.