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 detailed, unmasked information about a specific customer by their unique identifier. It is useful in scenarios where you need to fetch comprehensive customer data for verification, compliance checks, or account management within automated workflows. For example, a financial platform might use this node to obtain full customer details before processing transactions or updating records.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the customer to retrieve. This is a required string input. |
| Straddle Account Id | (Optional) Used by platforms to specify an account ID and set the scope of the request. |
| 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. |
Output
The node outputs JSON data representing the full unmasked customer details as returned by the Straddle API. This includes structured information such as:
- Customer's business profile, including address, industry, and support channels.
- Capabilities like supported payment types and customer types.
- Settings related to charges and payouts.
- Representative details including compliance information.
- Bank account details and verification status.
- Status messages and metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests depends on the configured environment (e.g., sandbox or production).
- Proper network access to
https://{environment}.straddle.iois necessary.
Troubleshooting
- Missing or invalid Id: Since the "Id" property is required, omitting it will cause errors. Ensure it is provided and correctly formatted.
- Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify credentials are correctly set up.
- Network issues: Connectivity problems to the Straddle API endpoint can cause timeouts or failures.
- Header misconfiguration: Optional headers like "Straddle Account Id", "Request Id", and "Correlation Id" should be used carefully; incorrect values may affect request scoping or tracing.
- API rate limits or permissions: The user’s API key must have permission to access customer data; otherwise, authorization errors may occur.
Links and References
- Straddle API Documentation (general reference for API endpoints and data models)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes