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 bridge connection using Plaid tokens. Specifically, the post__v1_bridge_plaid operation allows users to link a customer's financial data via a Plaid processor token. This is useful in scenarios where platforms want to securely connect customer bank accounts or financial information through Plaid and manage it within the Straddle ecosystem.
Practical examples include:
- Financial platforms onboarding customers by linking their bank accounts via Plaid.
- Payment processors needing to verify and access customer account details securely.
- Applications that require syncing customer financial data from Plaid into Straddle for further processing.
Properties
| Name | Meaning |
|---|---|
| Straddle Account Id | For use by platforms to specify an account id and set scope of a request (sent as HTTP header). |
| 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). |
| Customer Id | Required. Unique identifier of the related customer object (sent in request body). |
| Plaid Token | Required. Plaid processor token generated by your application for use with the Straddle API (request body). |
| Metadata | User-defined key-value pairs as JSON object for custom metadata (sent in request body). |
Output
The node outputs JSON data representing the response from the Straddle API after creating the bridge with the provided Plaid token. The exact structure depends on the API response but typically includes details about the linked customer, status, and any relevant metadata.
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 the user to provide a valid Plaid processor token generated externally by their application.
- Proper network connectivity to the Straddle API endpoint is necessary.
Troubleshooting
- Invalid or expired Plaid token: The API may reject the request if the Plaid token is invalid or expired. Ensure the token is freshly generated and correctly passed.
- Missing required fields: Errors will occur if
customer_idorplaid_tokenare not provided. Always supply these mandatory properties. - Authentication errors: If the API key credential is missing or incorrect, authentication failures will happen. Verify the API key configuration.
- Header misconfiguration: Custom headers like
Straddle-Account-Id,Request-Id, andCorrelation-Idshould be strings; improper formatting might cause issues. - API environment mismatch: The base URL depends on the environment setting; ensure it matches the intended Straddle environment (e.g., sandbox vs production).
Links and References
- Straddle API Documentation (general reference for API endpoints and usage)
- Plaid Developer Documentation (for generating and managing Plaid tokens)
- n8n documentation on HTTP Request Node for understanding how headers and body routing works in custom nodes.