> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/connect-to-systems/connectors/html-to-pdf.md).

# HTML to PDF

In Flow Classic, the HTML to PDF connector was used to generate PDF files within workflows. The connector utilized HyperText Markup Language (HTML) to define the layout of PDF pages.

In Flow Connect, the HTML to PDF connector has been replaced by two dedicated operations available under the File System connector. This means that, as a Flow developer, you no longer need to create a separate connector. Instead, simply use the File System connector and select the appropriate operation as described below.

## Operations

| PDF Operations                                                                                                | Description                            |
| ------------------------------------------------------------------------------------------------------------- | -------------------------------------- |
| [HTML to PDF](/flow-connect/reference/reference/flowscript/walkthrough/filesystem-module.md#converthtmltopdf) | Converts HTML content to PDF           |
| [Merge PDF](/flow-connect/reference/reference/flowscript/walkthrough/filesystem-module.md#mergepdfs)          | Merges two PDF files into a single PDF |


---

# 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.novacura.com/flow-connect/working-with-connect/connect-to-systems/connectors/html-to-pdf.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.