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 unmasked details of a specific representative by their unique identifier. It is useful in scenarios where you need to access detailed, sensitive information about a representative that is normally masked for privacy reasons, such as compliance checks, identity verification, or detailed reporting.
For example, a financial service platform might use this node to fetch full representative details during onboarding or audit processes, ensuring they have accurate and complete data.
Properties
| Name | Meaning |
|---|---|
| Representative Id | The unique identifier of the representative whose unmasked details are to be retrieved. |
| 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 containing the full unmasked details of the specified representative. This includes comprehensive information such as:
- Address details (line1, line2, city, state, postal code, country)
- Compliance profile (date of birth, last 4 digits of SSN, ID document details)
- Bank account details (routing number, masked account number, account type, bank name)
- Status and verification details
- Other metadata fields relevant to the representative's profile
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., production or sandbox).
- Proper network connectivity to the Straddle API endpoint.
Troubleshooting
- Missing or invalid Representative Id: Ensure the Representative Id property is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Rate limiting or API errors: If the API returns errors related to rate limits or server issues, consider implementing retries or checking API status.
- Header tracing IDs not working: If using Request Id or Correlation Id headers for debugging, ensure these values are unique and properly propagated.
Common error messages may include unauthorized access, resource not found (if the representative ID does not exist), or validation errors for malformed input.
Links and References
- Straddle API Documentation (general reference for API endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.