Overview

This node interacts with the Billing Booth One API to retrieve customer transaction data using cursor-based pagination. It supports fetching transactions with various filters such as date ranges, organisation ID, ledger entry types, and pagination controls like next and previous cursors, page size, and offset. This node is useful for workflows that need to process or analyze customer transaction records in a paginated manner, for example, financial reporting, auditing, or syncing transaction data to other systems.

Use Case Examples

1. Retrieve a page of customer transactions starting from a specific cursor to process recent transactions.
2. Filter customer transactions by organisation ID and date range to generate a report for a specific period.
3. Use pagination options like next_cursor and page_size to iterate through all customer transactions in batches.

Properties

Output

JSON

• data - The retrieved customer transaction data from the Billing Booth One API.

Dependencies

• Billing Booth One API

Troubleshooting

• Ensure the API credentials are correctly configured and have the necessary permissions to access customer transaction data.
• Verify that the base URL for the API is correct and accessible from the n8n environment.
• Check that the cursor and pagination parameters are valid numbers to avoid request errors.
• If the node returns an error about missing routing information, confirm that the resource and operation parameters are correctly set to 'Customers' and 'Get Customer Transactions By Cursor'.
• Handle API rate limits or network issues by enabling 'Continue On Fail' to allow the workflow to proceed despite intermittent errors.