Actions108
- AI Actions
- Transcribe
- Detect Brand
- Extract Contact Information
- Mood Detection
- Detect Adult Content
- Enitity Detection
- Language Detection
- Too Long To Read
- Check Content Policy
- Detect Faces
- Generate Python Code
- Picture Text Recognition
- Detect Color
- Generate Image
- PDF OCR
- Translation
- Detect Email Type
- Generate Javascript Code
- Picture Object Recognition
- Business Actions
- Calculate Actions
- Code Actions
- Convert Actions
- Crypto Actions
- Date & Time Actions
- Generate Actions
- Image Actions
- Operator Actions
- PDF Actions
- Storage Actions
- Text Actions
- User Actions
Overview
The node "0CodeKit" provides a versatile toolbox of no-code utilities across multiple domains, including PDF processing. Specifically, the PDF to Base64 operation converts a given PDF file (provided as a public URL or a buffer string) into its Base64-encoded representation. This is useful when you need to embed PDFs directly into JSON payloads, transmit them over text-based protocols, or store them in systems that require Base64 encoding.
Common scenarios:
- Embedding PDF content into emails or API requests.
- Storing PDF data in databases that accept only text fields.
- Passing PDF files between systems without using binary attachments.
Practical example:
You have a PDF hosted on a public URL and want to convert it to Base64 to send it as part of a webhook payload. Using this node, you input the URL and receive the Base64 string output, ready for transmission.
Properties
| Name | Meaning |
|---|---|
| Code Variables | A collection of code variables defined in the code editor for selected functions. Each variable has a name/ID and a value. Useful for dynamic scripting within the node. |
| The PDF input, which can be either a public URL pointing to the PDF file or a Buffer String representing the PDF content. Required for the PDF to Base64 operation. | |
| Filename | The filename of the PDF. Optional but useful for identification or downstream processing. |
Output
The node outputs a JSON array where each item corresponds to an input item processed. For the PDF to Base64 operation, the key output is:
base64: A string containing the Base64-encoded representation of the input PDF file.
If the node supports binary data output for other operations, it would typically represent the PDF content in binary form, but for this operation, the focus is on Base64 string output.
Dependencies
- Requires an API key credential for authentication with the external 0CodeKit service.
- The node makes HTTP POST requests to the 0CodeKit API endpoint corresponding to the PDF resource and base64 operation.
- No additional environment variables are explicitly required beyond the API key credential.
Troubleshooting
- Invalid PDF input: If the provided PDF URL is inaccessible or the buffer string is malformed, the node may throw errors related to fetching or decoding the PDF. Ensure the URL is publicly accessible or the buffer string is correctly formatted.
- Authentication errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is properly configured.
- Unexpected response format: If the API changes or returns unexpected data, the node might fail to parse the Base64 string. Check the API status and update the node if necessary.
- Continue On Fail: The node supports continuing execution on failure for individual items, allowing partial success in batch operations.
Links and References
- n8n Expressions Documentation — for using expressions in variable definitions.
- 0CodeKit API documentation (not publicly linked here) — refer to your API provider's docs for detailed API usage.
Note: Internal credential names and specific API endpoints are abstracted per guidelines.