HTML 2 PDF integration. Manage Documents, Templates. Use when the user wants to interact with HTML 2 PDF data.
HTML 2 PDF is a service that converts HTML documents into PDF files. Developers and businesses use it to generate PDFs from web pages, templates, or HTML code. It simplifies the process of creating printable or archivable documents.
Official docs: https://html2pdf.app/en/documentation
This skill uses the Membrane CLI to interact with HTML 2 PDF. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search html-2-pdf --elementType=connector --json
Take the connector ID from output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
The user completes authentication in the browser. The output contains the new connection id.When you are not sure if connection already exists:
membrane connection list --json
If a HTML 2 PDF connection exists, note its connectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| Get Usage | get-usage | Get account usage statistics including plan limits and current usage counts. |
| Convert HTML to PDF | convert-html-to-pdf | Convert raw HTML content to a PDF document with customizable page settings, headers, footers, and security options. |
| Convert URL to PDF | convert-url-to-pdf | Convert a webpage URL to a PDF document with customizable page settings, headers, footers, and security options. |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the HTML 2 PDF API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.