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 Straddle API to retrieve detailed information about a specific funding event by its unique identifier. It is useful in financial workflows where you need to fetch and process data related to individual funding events, such as payment settlements or account funding transactions.
Typical use cases include:
- Retrieving details of a particular funding event for reconciliation or auditing.
- Integrating funding event data into downstream systems like accounting or reporting tools.
- Debugging or tracing specific funding events using optional request identifiers.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the funding event to retrieve. This is a required string input. |
| Straddle Account Id | (Optional) For platforms to specify an account ID to scope the request. Sent as a header. |
| Request Id | (Optional) Client-generated identifier to trace and debug this specific request. Header. |
| Correlation Id | (Optional) Client-generated identifier to trace and debug a series of related requests. Header. |
Output
The node outputs JSON data representing the funding event details retrieved from the Straddle API. The structure includes all relevant fields describing the funding event, such as amounts, timestamps, status, and associated metadata.
No binary data output is produced by 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 sends HTTP requests with
Accept: application/jsonandContent-Type: application/jsonheaders.
Troubleshooting
- Missing or invalid Id: Since the "Id" property is required, omitting it or providing an incorrect value will cause the API call to fail. Ensure the correct funding event ID is provided.
- Authentication errors: If the API key credential is missing or invalid, the request will be unauthorized. Verify that the API key is correctly configured.
- Request tracing headers: Optional headers like Request Id and Correlation Id help with debugging but are not mandatory. Incorrect usage won't break the request but may reduce traceability.
- Network or environment issues: Ensure the environment variable used to construct the base URL is correctly set to avoid connection failures.
Links and References
- Straddle API Documentation (general reference for API endpoints and data models)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes