Actions55
- Webhooks Actions
- Payments Actions
- Products Actions
- Plans Actions
- Partner Referrals Actions
- Reporting Actions
- Orders Actions
- Subscriptions Actions
- Invoicing Actions
- Disputes Actions
Reporting → List Transactions
AI-generatedOverview
This node provides an enhanced integration with PayPal, supporting over 70 operations across multiple PayPal resources such as Orders, Subscriptions, Invoicing, Disputes, Webhooks, Payments, Products, Plans, Partner Referrals, and Reporting. Specifically, the Reporting - List Transactions operation allows users to retrieve a list of transaction history from their PayPal account.
This node is beneficial for automating financial reporting workflows, reconciling transactions, auditing payment histories, or integrating PayPal transaction data into other systems like accounting software or dashboards.
Practical example:
A business can use this node to automatically fetch all PayPal transactions within a specified date range and page size, then process or store that data in a database or spreadsheet for monthly financial reports.
Properties
| Name | Meaning |
|---|---|
| Additional Options | Collection of optional parameters: |
| - Environment: Choose between "Sandbox" (test) or "Live" PayPal environment | |
| - Page Size: Number of transactions to return per page (default 20) | |
| - Start Time: ISO 8601 formatted start date/time to filter transactions | |
| - End Time: ISO 8601 formatted end date/time to filter transactions |
Output
The output JSON contains the following fields:
resource: The resource name, here always"reporting".operation: The operation performed, here"listTransactions".success: Boolean indicating if the API call was successful.- Transaction data fields returned by PayPal's
/v1/reporting/transactionsendpoint, which typically include transaction details such as IDs, amounts, statuses, timestamps, payer info, etc. creditsUsed: Number of API credits consumed by the request (usually 1).creditsRemaining: Remaining API credits available.timestamp: ISO string timestamp when the response was received.
No binary data output is produced by this operation.
Dependencies
- Requires two credentials configured in n8n:
- An API key credential for the external "N8N Tools API" service used for validation.
- A PayPal OAuth2 API credential providing an access token and environment setting.
- The node makes HTTP requests to both the N8N Tools API and PayPal REST API endpoints.
- Proper configuration of these credentials with valid API keys and tokens is necessary.
Troubleshooting
- Invalid JSON in Request Body: If a JSON input property is malformed, the node throws an error specifying invalid JSON. Ensure JSON syntax correctness.
- API Validation Failure: If the N8N Tools API validation fails, the node will throw an error indicating validation failure. Check API key validity and network connectivity.
- Unknown Operation or Resource: Errors occur if unsupported operations or resources are selected. Verify correct resource-operation combinations.
- Authorization Errors: If PayPal OAuth2 token is invalid or expired, API calls will fail. Refresh or reauthenticate the PayPal credential.
- Rate Limits / Credits: The node tracks API credits used and remaining; hitting limits may cause failures. Monitor usage accordingly.