CraftMyPdf icon

CraftMyPdf

Consume the CraftMyPDF API

Actions7

Overview

The node integrates with the CraftMyPDF API to perform PDF-related operations. Specifically, for the PDF - Merge operation, it merges multiple PDF files from given URLs into a single PDF document. This is useful when you have several separate PDFs (e.g., reports, invoices, contracts) hosted online and want to combine them into one consolidated file for easier sharing or archiving.

Practical examples:

  • Combining multiple invoice PDFs generated daily into a single monthly statement.
  • Merging various contract documents received as separate PDFs into one file before sending to a client.
  • Aggregating different sections of a report stored as individual PDFs into a unified document.

Properties

Name Meaning
Region The API endpoint region to use. Options include Default, Australia, Europe (Frankfurt), US East (N. Virginia), alternative endpoints for Europe, Singapore, US East, and a staging environment.
Expiration The lifetime in minutes for which the generated merged PDF will be available before expiring. Must be between 1 and 10080 minutes (7 days).
Output File The filename for the resulting merged PDF file, e.g., output.pdf.
URL Array A collection of URLs pointing to the individual PDF files to merge. Each entry requires a valid URL string of a PDF document accessible by the API.

Output

The output JSON contains information about the merged PDF file generated by the API. Depending on the export type configured (usually "file"), the node returns either:

  • A JSON object describing the merged PDF metadata and access details.
  • Or binary data representing the actual merged PDF file content ready for further workflow processing or saving.

The exact structure depends on the API response but typically includes the merged PDF's URL or file data and related metadata such as expiration time and filename.

Dependencies

  • Requires an active connection to the CraftMyPDF API via an API key credential.
  • The node must be configured with appropriate API credentials and network access to the specified regional endpoints.
  • The input URLs must be publicly accessible or accessible by the API service to fetch the source PDFs.

Troubleshooting

  • Invalid URLs: If any URL in the URL array is invalid or inaccessible, the merge operation may fail. Ensure all URLs point to valid PDF files reachable by the API.
  • Expiration limits: Setting expiration outside the allowed range (1 to 10080 minutes) will cause errors. Use values within this range.
  • API authentication errors: Missing or incorrect API credentials will prevent successful requests. Verify that the API key is correctly set up.
  • File size or count limits: The API might impose limits on the number or size of PDFs merged; exceeding these can cause failures.
  • JSON validation errors: Input parameters like URLs must be properly formatted; malformed inputs can trigger errors.

If the node throws errors related to invalid JSON or missing parameters, double-check the input property formats and required fields.

Links and References

Discussion