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 account by its unique Account Id. It is useful in scenarios where you need to fetch up-to-date account data such as business profile, capabilities, settings, bank details, verification status, and support channels from the Straddle platform.
Practical examples include:
- Automating workflows that require validation or enrichment of account information.
- Integrating account data retrieval into customer service or compliance processes.
- Building dashboards or reports that display real-time account details.
Properties
| Name | Meaning |
|---|---|
| Account Id | The unique identifier of the account to retrieve. |
| Request Id | Optional client-generated identifier to trace and debug a single request (sent as header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (header). |
Output
The node outputs JSON data representing the full account object retrieved from the Straddle API. The structure includes comprehensive account details such as:
- Business Profile: Address, industry, support channels.
- Capabilities: Supported payment types (ACH, card, wire), customer types (individual, business), consent types.
- Settings: Charge and payout configurations.
- Representative: Address and compliance profile including DOB, SSN, ID documents.
- Linked Bank Account: Bank details, status, and verification info.
- Paykey Data: Bank data and status details.
- Metadata: Custom user-defined key-value pairs.
- Status Details: Messages, reasons, sources, and timestamps for status changes.
- Verification: Status, method, attempts, and completion time.
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 credential parameter.
- The node sends HTTP requests with JSON content type and expects JSON responses.
Troubleshooting
- Invalid Account Id: If the provided Account Id does not exist or is malformed, the API will likely return an error. Verify the Account Id value before running the node.
- Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network Issues: Connectivity problems or incorrect environment configuration can cause request failures.
- Missing Headers: Optional headers like Request Id and Correlation Id are for tracing; omitting them should not cause errors but including them helps debugging.
Common error messages may relate to unauthorized access, resource not found, or bad request due to invalid parameters. Checking the exact API response message and verifying input values usually resolves these issues.
Links and References
- Straddle API Documentation (hypothetical link)
- n8n HTTP Request Node documentation for understanding request routing and headers
- General API authentication best practices