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 information about a specific customer by their unique identifier. It is useful in scenarios where you need to fetch customer data for processing, verification, or integration purposes within an automation workflow. For example, you might use this node to pull customer details before initiating a payment, updating records, or performing compliance checks.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the customer to retrieve. |
| 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 customer's full profile as returned by the Straddle API. This includes structured information such as:
- Business profile and address details
- Industry and support contact information
- Capabilities like supported payment types and customer types
- Settings related to charges and payouts
- Bank account details and verification status
- Status messages and metadata
The output does not include binary data; it is purely JSON structured data describing the customer.
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).
- No additional external dependencies are indicated.
Troubleshooting
- Missing or invalid Id: Since the
Idproperty is required, omitting it or providing an incorrect value will likely cause the API call to fail. Ensure the correct customer ID is provided. - Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify that the API key is correctly configured.
- Request tracing headers: Optional headers like
Request IdandCorrelation Idhelp with debugging but do not affect functionality. Incorrect usage should not break the node but may reduce traceability. - API endpoint issues: Ensure the environment parameter used to build the base URL is valid and reachable.
Links and References
- Straddle API Documentation (Assumed official docs for further details)
- n8n documentation on HTTP Request Node for understanding API integrations in workflows