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 charge by its unique identifier. It is useful in scenarios where you need to fetch and process payment charge data, such as verifying transaction details, auditing payments, or integrating charge information into workflows for further processing or reporting.
For example, you might use this node to:
- Retrieve the status and metadata of a particular charge after a payment attempt.
- Fetch charge details to reconcile transactions in your accounting system.
- Use charge information to trigger conditional logic based on payment success or failure.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the charge to retrieve (required). |
| Straddle Account Id | Optional header to specify an account ID for scoping the request, typically used by platforms. |
| Request Id | Optional client-generated identifier to trace and debug the individual request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
Output
The node outputs JSON data representing the full details of the requested charge. This includes all relevant fields returned by the Straddle API for a charge resource, such as amount, status, timestamps, metadata, and any nested objects describing the charge's context.
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 environment specified in the credentials.
- The node expects the Straddle API to be accessible and properly configured for the given environment.
Troubleshooting
- Missing or invalid charge Id: Ensure the "Id" property is provided and correctly references an existing charge.
- Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- Network or connectivity issues: Confirm that the environment URL is correct and reachable.
- Request tracing headers: If using "Request Id" or "Correlation Id", ensure they are unique and consistent to aid debugging.
- API rate limits or errors: Handle API error responses gracefully; check Straddle API documentation for error codes and retry policies.
Links and References
- Straddle API Documentation (general reference for API endpoints and data structures)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes