Actions62
- SQL Actions
- Client Access Actions
- User Access Actions
- Tools Actions
- HTML to PDF
- Markdown to PDF
- Text to PDF
- Merge PDFs
- Split PDF
- Extract PDF Text
- Resize Image
- Convert Image
- Compress Image
- Add Image Watermark
- Create Thumbnail
- Generate Barcode
- Read Barcode
- Validate CPF/CNPJ
- Format CPF/CNPJ
- Generate UUID
- Transform JSON
- CSV to JSON
- JSON to CSV
- Normalize Text
- Extract Regex Fields
- Validate JSON Schema
- Generate Hash
- HMAC Sign
- Base64 Encode/Decode
- JWT Decode
- Encrypt Text
- Decrypt Text
- Format Date
- Parse Date
- Add Business Days
- Format Currency
- Number to Words
- Build Socket Event Payload
- Validate Client Token
- Validate Agent Context
- Build SQL Request
- Parse SQL Rows
- Generate Access Request Summary
- Publish Socket Event
- Wait for Socket Event
Tools → Text to PDF
AI-generatedSummary
Convert a text string into a PDF file with customizable browser rendering and PDF settings, storing the result as binary data in the specified property.
Inputs
- Tool Category — Select the category of tools to show (default is 'Documents').
- Text (required) — Input text to convert into PDF content.
- File Name — Filename for the generated PDF file (default: 'document.pdf').
- Output Binary Property — Name of the binary property where the PDF file binary will be stored (default: 'data').
- Browser Options — Options to control browser executable path, browser channel (Chromium, Chrome, Edge), timeouts, and whether to enable JavaScript during rendering.
- PDF Options — Settings to control PDF format (A3, A4, etc.), orientation, background printing, scaling, wait conditions, margins, header/footer HTML templates, maximum sizes, and other advanced print options.
- Include Plug Tools Metadata — Whether to include internal metadata about the operation in the result (default: true).
- Metadata Property — Name of the property to store internal metadata if included (default: '__plugTools').
Output shape
a single binary output item containing the generated PDF file.
The generated PDF binary is stored under the specified output binary property in the node's output. The operation supports customizing browser rendering behavior and PDF options to fit formatting needs. Metadata inclusion is optional and can be controlled with dedicated properties.