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 a review of a specific customer by their unique identifier. It is designed to fetch detailed information about a customer's review status or data from the Straddle platform.
Common scenarios where this node is beneficial include:
- Automating workflows that require fetching customer review details for compliance or verification purposes.
- Integrating customer review data into CRM systems or dashboards.
- Triggering downstream processes based on the review status of a customer.
For example, after onboarding a customer, you might use this node to periodically check their review status and update your internal records accordingly.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the customer whose review information you want to retrieve. |
| Straddle Account Id | (Optional) Used by platforms to specify an account ID to set the scope of the request. |
| Request Id | (Optional) Client-generated identifier to trace and debug the individual request. |
| Correlation Id | (Optional) Client-generated identifier to trace and debug a series of related requests. |
Output
The node outputs JSON data representing the customer's review information as returned by the Straddle API. This includes structured details about the customer's profile, compliance, capabilities, settings, bank details, status, and verification information.
The output JSON structure contains nested objects describing various aspects such as:
- Business profile and address
- Compliance profile including date of birth and social security number fragments
- Supported payment types and customer types
- Account settings like charges and payouts
- Bank account details and verification status
- Status messages and reasons for current state
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 depends on the configured environment (e.g., sandbox or production).
- Proper network access to the Straddle API endpoint is necessary.
Troubleshooting
- Missing or invalid Id: Since the
Idproperty is required, omitting it will cause the request to fail. Ensure the customer ID is correctly provided. - Authentication errors: If the API key credential is missing or invalid, the node will return authentication errors. Verify the API key configuration.
- Rate limiting or quota exceeded: The Straddle API may enforce rate limits; if exceeded, requests will be rejected. Implement retry logic or reduce request frequency.
- Incorrect environment setting: The base URL depends on the environment parameter in credentials. Using the wrong environment can lead to connection failures.
- Header misconfiguration: Optional headers like
Straddle Account Id,Request Id, andCorrelation Idshould be used carefully to avoid request rejection or tracing issues.
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 n8n nodes.