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 updates the status of a linked bank account within a financial or payment platform. It allows users to change the lifecycle state and detailed verification status of a specific linked bank account by providing its unique identifier and new status values.
Common scenarios where this node is beneficial include:
- Managing onboarding workflows for bank accounts, such as moving an account from "created" to "active" after verification.
- Marking accounts as "rejected" or "inactive" based on compliance or user actions.
- Tracking detailed verification states like "pending", "verified", or "failed verification" to reflect the current verification progress.
Practical example:
- A business automates their bank account management by updating the status of newly linked accounts to "onboarding" when they start verification, then to "active" once verified, or to "rejected" if verification fails.
Properties
| Name | Meaning |
|---|---|
| Linked Bank Account Id | The unique identifier of the linked bank account whose status is to be updated. |
| Request Id | Optional client-generated identifier to trace and debug a single request (sent as HTTP header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (HTTP header). |
| Status | The new high-level status of the linked bank account. Possible values: Created, Onboarding, Active, Rejected, Inactive. |
| Status Detail | The detailed verification or processing status of the linked bank account. Possible values: Unverified, In Review, Pending, Stuck, Verified, Failed Verification, Disabled. |
Output
The node outputs JSON data representing the updated linked bank account resource. This includes fields such as:
bank_details: Information about the bank account (routing number, masked account number, account type, bank name).status_details: Details about the current status including message, reason, source, and timestamp of last change.verification: Verification information such as status, method used, number of attempts, and completion time.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the external Straddle API service.
- The base URL for API requests depends on the configured environment credential parameter.
- Proper configuration of HTTP headers including optional tracing headers (
request-id,correlation-id) is supported.
Troubleshooting
- Invalid Linked Bank Account Id: If the provided ID does not exist or is malformed, the API will likely return an error indicating the resource was not found.
- Unauthorized Access: Missing or invalid API authentication token will cause authorization errors.
- Invalid Status or Status Detail Values: Providing unsupported status strings may result in validation errors.
- Network Issues: Connectivity problems can cause request failures; ensure network access to the API endpoint.
- To resolve errors, verify all required properties are correctly set, check API credentials, and consult API documentation for valid status values.
Links and References
- Straddle API Documentation (hypothetical link for reference)
- n8n HTTP Request Node documentation for understanding how headers and body routing works.