Actions19
- AI Invoice Parser
- URL/HTML to PDF
- Merge PDF
- Split PDF
- Convert To PDF
- Convert From PDF
- Add Text/Images to PDF
- Fill a PDF Form
- PDF Information & Form Fields
- Compress PDF
- PDF Security
- Rotate PDF Pages
- Delete PDF Pages
- Search in PDF
- Search & Replace Text or Delete
- Barcode Reader
- Barcode Generator
- Make PDF Searchable or Unsearchable
- Upload File
Overview
This node integrates with a PDF processing service to make PDF files either searchable or unsearchable. It is particularly useful for workflows that involve scanned documents or image-based PDFs where text extraction is needed (making them searchable), or conversely, when you want to obscure or remove searchable text from PDFs (making them unsearchable).
Common scenarios include:
- Converting scanned PDFs into searchable documents using OCR (Optical Character Recognition).
- Securing PDFs by removing searchable text layers.
- Automating document processing pipelines where PDFs need to be prepared for indexing or redaction.
For example, you might use this node to convert a batch of scanned invoices into searchable PDFs so their content can be indexed and searched in your document management system.
Properties
| Name | Meaning |
|---|---|
| PDF URL | The URL of the PDF file to process (make searchable or unsearchable). |
| Make PDF Searchable or Unsearchable | Choose whether to make the PDF searchable (add OCR text layer) or unsearchable (remove text layer). Options: "Make PDF Searchable", "Make PDF Unsearchable". |
| OCR Language Name or ID | When making the PDF searchable, specify the language for OCR text extraction. You can select from a predefined list or provide an expression with a language ID. |
| Advanced Options | A collection of optional settings: |
| File Name | Name for the output PDF file. |
| Pages | Specify page numbers or ranges to process (e.g., "0,1-2,5,7-"). |
| Webhook URL | URL to receive callback notifications or output data asynchronously. |
| Output Links Expiration (In Minutes) | Duration before generated output links expire (default 60 minutes). |
| Password | Password for encrypted PDF files if required to access or modify them. |
| HTTP Username | HTTP username if the source PDF URL requires authentication. |
| HTTP Password | HTTP password corresponding to the HTTP username for accessing the source PDF. |
| Custom Profiles | JSON string to specify custom API call options or profiles for advanced configurations. See the external API documentation for available profile settings. |
Output
The node outputs JSON data containing information about the processed PDF. This typically includes URLs or base64 encoded data of the resulting PDF file after making it searchable or unsearchable.
If the node supports binary data output, it would represent the processed PDF file itself, allowing downstream nodes to handle or save the file directly.
Dependencies
- Requires access to an external PDF processing API service capable of OCR and PDF manipulation.
- Needs an API key or authentication token configured in n8n credentials to authorize requests to the PDF service.
- Internet access to fetch the source PDF from the provided URL.
- Optional webhook endpoint if asynchronous callbacks are used.
Troubleshooting
- Invalid PDF URL or inaccessible file: Ensure the URL is correct and publicly accessible or that HTTP authentication credentials are correctly provided.
- Incorrect OCR language setting: If OCR results are poor or fail, verify the selected language matches the document's language.
- Expired output links: If output links expire before retrieval, increase the expiration time in advanced options.
- Authentication errors: Confirm that the API key credential is valid and has necessary permissions.
- Malformed custom profiles JSON: Validate JSON syntax when using custom profiles to avoid API call failures.
Links and References
- PDF.co API Profiles Documentation
- n8n Expressions Documentation (for dynamic property values)