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 "Charge" resource of the Straddle API, specifically performing the operation to release a charge by its ID (put__v1_charges_id_release). The operation sends a request to release a previously held or authorized charge, optionally providing a reason for the release.
Common scenarios where this node is useful include:
- Releasing a payment hold on a customer's charge after review.
- Cancelling an authorized but not yet captured payment.
- Automating charge management workflows in payment processing systems.
For example, after verifying that a charge should no longer be held, you can use this node to release it programmatically, optionally specifying a reason such as "Customer requested cancellation" or "Fraud check failed".
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the charge to release. |
| Straddle Account Id | (Optional) For platforms: specifies an account ID to set the scope of the request via 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). |
| Reason | (Optional) Textual reason explaining why the charge is being released (sent in request body). |
Output
The node outputs JSON data representing the response from the Straddle API after releasing the charge. This typically includes details about the updated charge status and any relevant metadata returned by the 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 constructed based on the configured environment credential parameter.
- The node expects the
AcceptandContent-Typeheaders to be set toapplication/json.
Troubleshooting
- Missing or invalid charge Id: Ensure the "Id" property is provided and corresponds to an existing charge.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Invalid headers: If using optional headers like
Straddle Account Id,Request Id, orCorrelation Id, ensure they are correctly formatted strings. - API errors: The API may return errors if the charge cannot be released (e.g., already released or invalid state). Check the error message for details.
- Network issues: Confirm network connectivity to the Straddle API endpoint and correct environment configuration.
Links and References
- Straddle API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding how API calls are made within n8n)
If you need further details on other operations or resources, feel free to ask!