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 integrates with the Straddle API to create a linked bank account for a customer via the Bridge resource. Specifically, the post__v1_bridge_bank_account operation allows users to submit bank account details (routing number, account number, and type) associated with a given customer ID. This is useful in scenarios where platforms or applications need to programmatically link customers' bank accounts for payments, payouts, or verification purposes.
Practical examples include:
- A financial platform onboarding new customers by linking their bank accounts.
- Automating the process of adding bank accounts for payment disbursements.
- Verifying bank account information before enabling transactions.
Properties
| Name | Meaning |
|---|---|
| Straddle Account Id | Optional header to specify an account id and set the scope of the request (for platform use). |
| Request Id | Optional client-generated identifier to trace and debug a single request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
| Customer Id | Required. Unique identifier of the related customer object to whom the bank account belongs. |
| Routing Number | Required. The bank routing number of the account being linked. |
| Account Number | Required. The bank account number to be linked. |
| Account Type | Required. Type of bank account; options are: Checking, Savings. |
| Metadata | Optional user-defined key-value pairs as JSON to attach custom metadata to the request. |
Output
The node outputs JSON data representing the response from the Straddle API after creating the linked bank account. The output includes detailed information about the linked bank account such as:
- Bank details (masked account number, routing number, account type, bank name).
- Status details including messages, reasons, and sources for the current status.
- Verification details like status, method used, number of attempts, and completion timestamp.
- Additional metadata or related fields 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.
- The node expects JSON content-type headers and uses standard REST API calls.
Troubleshooting
- Missing Required Fields: Ensure that
Customer Id,Routing Number,Account Number, andAccount Typeare provided; otherwise, the API will reject the request. - Invalid Bank Details: Incorrect routing or account numbers may cause verification failures or errors from the API.
- Authentication Errors: Verify that the API key credential is correctly configured and has appropriate permissions.
- Header Misconfiguration: Optional headers like
Straddle Account Id,Request Id, andCorrelation Idshould be strings if used; invalid formats might cause request issues. - JSON Parsing Errors: The
Metadatafield must be valid JSON; malformed JSON will cause errors when parsing before sending the request.
Links and References
- Straddle API Documentation (general reference for API endpoints and data models)
- Bank Account Linking Concepts (conceptual overview)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.