CraftMyPdf icon

CraftMyPdf

Consume the CraftMyPDF API

Actions7

Overview

The node integrates with the CraftMyPDF API to list transactions. It retrieves a paginated list of transaction records from the API, allowing users to specify how many results to return and where to start in the list (offset). This operation is useful for workflows that need to process or analyze batches of transaction data, such as financial reporting, auditing, or syncing transaction records with other systems.

Example use cases:

  • Fetching recent transactions for reconciliation.
  • Exporting transaction data for accounting purposes.
  • Monitoring transaction activity within a specified range.

Properties

Name Meaning
Region The API endpoint region to connect to. Options include: Default, Australia, Europe, US East, Alternative endpoints, and Staging.
Limit Maximum number of transaction records to return in one request. Must be at least 1.
Offset Number of transaction records to skip before starting to collect the results. Must be 0 or more.

Output

The output is a JSON array containing the transaction records returned by the API. Each item in the array corresponds to a transaction object as provided by the CraftMyPDF API's /list-transactions endpoint.

The structure of each transaction object depends on the API response but typically includes details such as transaction ID, date, amount, status, and other relevant metadata.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the CraftMyPDF API via an API key credential configured in n8n.
  • The node uses the selected regional API endpoint to send requests.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • Invalid API credentials or missing API key: The node will fail if the API key credential is not set up correctly. Ensure the API key is valid and properly configured.
  • Invalid region selection: Selecting an unsupported or incorrect region may cause connection errors. Verify the region matches the intended API endpoint.
  • Limit or offset out of bounds: Providing invalid values (e.g., negative numbers) for limit or offset will cause errors. Use values within allowed ranges.
  • API rate limits or connectivity issues: Network problems or hitting API rate limits can cause failures. Check network connectivity and API usage quotas.
  • Malformed responses or unexpected data: If the API returns unexpected data, the node might throw errors. Confirm the API service is operational and returning valid data.

Links and References

Discussion