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 updates an existing linked bank account by sending a PUT request to the API endpoint corresponding to the specified linked bank account ID. It is useful in scenarios where you need to modify or correct details of a previously linked bank account, such as updating bank account information or metadata associated with the linked account.
Practical examples:
- Correcting bank account details after a user submits incorrect information.
- Adding or updating metadata for tracking or categorization purposes.
- Changing bank account settings or attributes without unlinking and relinking the account.
Properties
| Name | Meaning |
|---|---|
| Linked Bank Account Id | The unique identifier of the linked bank account to update (required). |
| 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. |
| Bank Account | JSON object containing the updated bank account information. This must be a valid JSON string representing the bank account details. (required) |
| Metadata | JSON object containing user-defined key-value pairs for custom metadata. Must be a valid JSON string. |
Output
The node outputs the response from the API call in the json field of the output data. This typically includes the updated linked bank account object with its properties such as:
- Bank account details (routing number, account number masked, account type, bank name).
- Status details including messages, reasons, and sources of status changes.
- Verification details like status, method, attempts, and completion time.
- Metadata and other related fields reflecting the current state of the linked bank account.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the Straddle API.
- The base URL for the API is dynamically set based on the environment credential parameter.
- The node expects the API to accept and return JSON-formatted data.
- Proper network connectivity to the Straddle API endpoint is necessary.
Troubleshooting
- Invalid or missing Linked Bank Account Id: Ensure that the Linked Bank Account Id property is provided and correctly references an existing linked bank account.
- Malformed JSON in Bank Account or Metadata: The Bank Account and Metadata fields require valid JSON strings. Invalid JSON will cause parsing errors.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API errors: If the API returns errors (e.g., 400 Bad Request, 404 Not Found), check the correctness of the input data and the existence of the linked bank account.
- Request tracing: Use the optional Request Id and Correlation Id headers to trace and debug requests in logs or support tools.
Links and References
- Straddle API Documentation (assumed official docs for the API)
- n8n documentation on HTTP Request Node for general API interaction patterns