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 operation allows you to release a payout by sending a PUT request to the endpoint /v1/payouts/{id}/release. It is useful in scenarios where payouts have been created but require explicit release or approval before funds are transferred. For example, a platform managing multiple payouts can use this operation to programmatically release a specific payout once all conditions are met.
Practical examples:
- Releasing a scheduled payout after verifying compliance.
- Triggering payout release as part of an automated workflow after order fulfillment.
- Manually releasing a payout that was previously held for review.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the payout to be released (required). |
| Straddle Account Id | Optional header to specify an account ID and set the scope of the request (for platforms). |
| Request Id | Optional client-generated identifier to trace and debug this specific request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
| Reason | The reason for releasing the payout (required). |
Output
The output JSON contains the response from the API after attempting to release the payout. This typically includes details about the payout status, confirmation of release, or error information if the release failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL is dynamically constructed based on the environment credential parameter.
- The node sends HTTP PUT requests with JSON payloads and expects JSON responses.
Troubleshooting
- Missing or invalid payout Id: Ensure the "Id" property is correctly set to a valid payout identifier.
- Authentication errors: Verify that the API key credential is configured properly and has permissions to release payouts.
- Invalid or missing "Reason": The API requires a reason for releasing the payout; provide a meaningful string.
- Header issues: If using "Straddle Account Id", "Request Id", or "Correlation Id" headers, ensure they are correctly formatted strings.
- API errors: Check the response message for details if the release fails due to business logic or compliance restrictions.
Links and References
- Straddle API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request node documentation for understanding how headers and body routing work within n8n nodes.