Actions81
- Users Actions
- Organizations Actions
- Representatives Actions
- Bridge Actions
- Platforms Actions
- Tools Actions
- User Invites Actions
- Customers Actions
- Paykeys Actions
- Reports Actions
- Charge Actions
- Funding Events Actions
- Payments Actions
- Payout Actions
- Accounts Actions
- Get Account By Id
- put__v1_accounts_account_id
- Create Account
- get__v1_accounts
- post__v1_accounts_account_id_onboard
- post__v1_accounts_account_id_simulate
- patch__v1_internal_accounts_account_id
- get__v1_internal_accounts_account_id
- patch__v1_internal_accounts_account_id_status
- get__v1_internal_accounts_account_id_settings
- Capability Requests Actions
- Linked Bank Accounts Actions
Overview
This node interacts with the "Funding Events" resource of the Straddle API, specifically performing the operation to retrieve a list of funding events (get__v1_funding_events). It allows users to query and fetch paginated funding event data such as deposits and withdrawals, filtered and sorted by various criteria.
Typical use cases include:
- Retrieving recent deposit or withdrawal events for reconciliation or reporting.
- Filtering funding events by date range, type, or direction to analyze cash flow.
- Sorting results by transfer date, amount, or ID to prioritize or organize data.
For example, a user might fetch all deposit funding events created in the last month, sorted by transfer date ascending, to generate a report on incoming funds.
Properties
| Name | Meaning |
|---|---|
| Page Number | Results page number. Starts at 1. Default is 1. |
| Page Size | Number of results per page. Default is 100, max is 1000. |
| Sort By | Field to sort results by: Transfer Date, Id, or Amount. |
| Sort Order | Sort direction: Ascending (asc) or Descending (desc). |
| Created From | Filter results created from this date/time (ISO string). |
| Created To | Filter results created up to this date/time (ISO string). |
| Direction | Funding event direction: Deposit or Withdrawal. |
| Event Type | Type of funding event: Charge Deposit, Charge Reversal, Payout Return, or Payout Withdrawal. |
| Trace Number | Trace number to filter specific transactions. |
| Straddle Account Id | Optional header to specify an account ID and scope the request (for platform use). |
| Request Id | Optional client-generated identifier to trace/debug the request (header). |
| Correlation Id | Optional client-generated identifier to trace/debug a series of requests (header). |
Output
The node outputs JSON data representing the retrieved funding events. Each item in the output corresponds to a funding event record returned by the API, including details such as transfer date, amount, event type, direction, and other metadata provided by the Straddle API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests is dynamically set based on the configured environment credential.
- The node uses standard HTTP headers
Accept: application/jsonandContent-Type: application/json. - No additional external dependencies beyond the Straddle API and n8n's HTTP request capabilities.
Troubleshooting
- Empty or missing results: Verify that the filters (date range, event type, direction) are correctly set and that there are matching funding events in the account.
- Invalid pagination parameters: Ensure
Page Numberstarts at 1 andPage Sizedoes not exceed 1000. - Authentication errors: Confirm that the API key credential is valid and has appropriate permissions.
- Rate limiting or API errors: Check the API response messages; consider adding retry logic or adjusting request frequency.
- Header usage: If using
Straddle Account Id,Request Id, orCorrelation Idheaders, ensure values are correctly formatted strings.
Links and References
- Straddle API Documentation (general reference for Funding Events endpoints)
- n8n Documentation - Creating Custom Nodes
- Pagination and Filtering Best Practices