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 interacts with the Straddle API to retrieve internal bridge configuration data. Specifically, the get__v1_internal_bridge_config operation fetches configuration details related to a "Bridge" resource within the Straddle platform. This can be useful for platforms or services that need to programmatically access bridge configurations for account management, integration setup, or debugging purposes.
Practical examples include:
- A financial platform retrieving bridge configuration to verify account linkage settings.
- An integration service fetching bridge config to dynamically adjust workflows based on current bridge parameters.
- Debugging or auditing tools pulling bridge configuration metadata for compliance or troubleshooting.
Properties
| Name | Meaning |
|---|---|
| Straddle Account Id | For use by platforms to specify an account id and set scope of a request. |
| Request Id | Optional client-generated identifier to trace and debug a request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of requests. |
All these properties are sent as HTTP headers in the API request.
Output
The output JSON contains the bridge configuration data returned by the Straddle API. The structure is defined by the Straddle API schema and typically includes detailed nested objects describing business profiles, capabilities, settings, representative information, linked bank accounts, paykey details, metadata, device info, compliance profiles, industry info, support channels, bank details, status details, and verification information.
The output JSON fields provide comprehensive configuration and status information about the bridge, including:
- Business profile and address
- Supported payment types and customer types
- Charge and payout settings
- Representative compliance and address details
- Bank account and verification statuses
- Metadata and device information
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 using the environment specified in credentials (e.g.,
https://{environment}.straddle.io). - The node depends on the n8n OpenAPI integration utilities for request building and schema processing.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key credential is correctly configured and has appropriate permissions.
- Incorrect environment setting: Verify the environment parameter in credentials matches the target Straddle environment.
- Invalid or missing header values: If using
Straddle Account Id,Request Id, orCorrelation Id, ensure they are correctly formatted strings. - API errors or unexpected responses: Check network connectivity and API status; enable debug logging to trace request/response details.
- Schema resolution issues: The node processes and resolves complex nested schemas; if output is incomplete, verify the API schema version compatibility.
Links and References
- Straddle API Documentation (general reference for API endpoints and schema)
- n8n OpenAPI Node Integration (for understanding how OpenAPI-based nodes work)
This summary is based solely on static analysis of the provided source code and property definitions.