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 provides integration with the Straddle API, specifically enabling the user to perform a POST request to the internal bridge endpoint (/v1/internal/bridge/mx). This operation is useful for platforms that need to interact with Straddle's internal bridge functionality, likely related to financial account linking or data exchange.
Typical use cases include:
- Platforms managing multiple accounts and needing to scope requests to a specific account.
- Sending traceable requests with client-generated identifiers for debugging or correlation purposes.
- Submitting member-specific data to the Straddle service for processing.
For example, a platform could use this node to post member information to Straddle’s internal bridge while specifying the account context and including identifiers to track the request flow.
Properties
| Name | Meaning |
|---|---|
| Straddle Account Id | (Optional) Specifies an account ID to set the scope of the request. Used by platforms managing multiple accounts. |
| 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. |
| Member Guid | (Required) Unique identifier for the member; included in the request body to specify the target member. |
Output
The node outputs JSON data returned from the Straddle API after posting to the internal bridge endpoint. The exact structure depends on the API response but typically includes status information, any data returned by the bridge, or error details if the request failed.
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 requests is dynamically constructed based on the environment specified in credentials (e.g.,
https://{environment}.straddle.io). - The node expects JSON content-type headers and accepts JSON responses.
Troubleshooting
- Missing Required Property: If
Member Guidis not provided, the request will fail as it is required in the request body. - Authentication Errors: Ensure the API key credential is correctly configured and has access to the specified environment.
- Invalid Account Scope: Providing an incorrect or unauthorized
Straddle Account Idmay result in permission errors. - Request Tracing: Use
Request IdandCorrelation Idproperties to help trace and debug issues with the API provider. - API Endpoint Changes: Since this uses an internal bridge endpoint, changes in the Straddle API might affect functionality; verify compatibility if errors occur.
Links and References
- Straddle API Documentation (Assumed official docs for further details)
- n8n HTTP Request Node documentation for general usage patterns with APIs: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.