Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation retrieves deposit records associated with a specific fund account. It is useful for financial workflows where you need to track or analyze deposits made into fund accounts, such as reconciliation processes, reporting, or auditing transactions.
For example, you might use this node to:
- Fetch all deposits made to a particular fund account within a date range.
- Retrieve a paginated list of deposits for review or export.
- Apply complex filters to find deposits matching certain criteria (e.g., amount thresholds, dates).
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the fund account belongs. |
| Fund Account Id | Identifier of the specific fund account whose deposits are being retrieved. |
| Filter | JSON-stringified and URL-encoded filter expression object that conforms to a deposit filter schema. Used to specify conditions like date ranges or other deposit attributes. |
| Skip | Number of deposit records to skip from the beginning of the result set (for pagination). |
| Take | Maximum number of deposit records to return (for pagination). |
Output
The output contains a JSON array of deposit objects corresponding to the specified fund account and filter criteria. Each deposit object includes details such as deposit date, amount, and any other relevant metadata defined by the API.
If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses on JSON data representing deposits.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service managing fund accounts and deposits.
- The node uses HTTP requests to interact with the external API endpoint for fund account deposits.
- Proper base URL configuration for the API is necessary in the credentials.
Troubleshooting
- Missing or invalid Account Id / Fund Account Id: Ensure these identifiers are correctly provided; otherwise, the API will return errors or empty results.
- Malformed Filter JSON: The filter property must be a valid JSON string conforming to the expected schema. Invalid JSON or incorrect filter structure can cause request failures.
- Pagination issues: Setting
SkiporTakeincorrectly may lead to unexpected results or no data returned. - Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to read fund account deposits.
- API rate limits or connectivity problems: Network issues or API throttling can cause errors; check logs and retry policies.
Links and References
- Refer to the external API documentation for the fund accounts and deposits endpoints to understand filter schema and response structure.
- n8n documentation on using HTTP Request nodes and handling pagination may provide additional context for advanced usage.