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 account settings for a specific account. The operation get__v1_internal_accounts_account_id_settings fetches detailed configuration and status information about an account identified by its Account Id. This is useful in scenarios where you need to programmatically access or audit account configurations, such as charge and payout settings, compliance profiles, bank details, and supported capabilities.
Practical examples include:
- Automatically retrieving account settings to verify configuration before processing payments.
- Auditing account capabilities and limits in batch workflows.
- Debugging or monitoring account status and verification details.
Properties
| Name | Meaning |
|---|---|
| Account Id | The unique identifier of the account whose settings are to be retrieved. |
| Environment | The target environment for the request: either "Sandbox" for testing or "Production" for live. |
| Request Id | Optional client-generated identifier to trace and debug this specific request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
Output
The output JSON contains detailed account settings and metadata structured according to the Straddle API schema. Key fields include:
- metadata: Custom user-defined key-value pairs.
- device: Information about the device making the request (IP address, user agent).
- config: Configuration options related to the account.
- address: Business or personal address details.
- compliance_profile: Compliance-related information such as date of birth, SSN, EIN, legal business name, and website.
- capabilities: Supported payment types (ACH, card, wire) and customer types (individual, business).
- settings: Charge and payout settings including enabled flags and limits.
- industry: Industry classification details like Merchant Category Code (MCC), sector, and category.
- support_channels: Contact information for support (email, phone, URL).
- bank_details: Bank account information including routing number, masked account number, account type, and bank name.
- status_details: Status messages, reasons, sources, and timestamps related to the account's current state.
- verification: Verification status, method, attempts count, and completion timestamp.
- bank_data: Additional bank account data similar to bank_details.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The node uses the environment property to determine the base URL (
sandboxorproduction). - Proper network connectivity to the Straddle API endpoints is necessary.
Troubleshooting
- Missing or invalid Account Id: Ensure the Account Id is provided and correctly formatted; otherwise, the API will return an error.
- Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- Environment mismatch: Using the wrong environment (sandbox vs production) may cause unexpected results or failures.
- Rate limiting or API errors: If the API returns rate limit errors or other HTTP errors, consider implementing retries or checking API usage quotas.
- Request/Correlation Ids: These optional headers help trace issues in logs; if debugging, provide meaningful values.
Links and References
- Straddle API Documentation (assumed official docs)
- n8n documentation on HTTP Request Node for understanding API calls
- General best practices for API authentication and error handling in n8n workflows