StraddleInstall

Overview

This node operation retrieves user information by looking up a user via a unique authenticator ID. It is useful in scenarios where you need to fetch detailed user data based on an authenticator identifier, such as verifying user identity or fetching user profile details linked to a specific authentication method.

Practical examples include:

• Fetching user details during an authentication flow to validate the user's credentials.
• Retrieving user metadata for audit or compliance purposes.
• Integrating with systems that require user lookup by authenticator ID for authorization or personalization.

Properties

Output

The output JSON contains detailed user information associated with the given authenticator ID. The structure includes multiple nested objects describing various aspects of the user, such as:

• metadata: Custom key-value pairs defined by the user.
• device: Device information including IP address and user agent.
• config: Configuration options related to the user.
• address: User's address details (line1, line2, city, state, postal code, country).
• compliance_profile: Compliance-related information like date of birth, SSN last 4 digits, EIN, legal business name, and website.
• capabilities: Supported payment types (ACH, card, wire) and customer types (individual, business).
• settings: Account settings including charge and payout configurations.
• industry: Business industry information such as merchant category code, sector, and category.
• support_channels: Support contact info including email, phone, and URL.
• bank_details: Bank account details including routing number, masked account number, account type, and bank name.
• status_details: Status messages, reasons, sources, and timestamps related to the user's status.
• 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 requests to the external Straddle API.
• The base URL for API requests is dynamically constructed using the environment specified in the credentials.
• HTTP headers accept and send JSON content.
• Optional headers for request tracing (request-id and correlation-id) can be set.

Troubleshooting

• Missing or invalid Authenticator Id: Since this property is required, omitting it or providing an incorrect value will likely cause errors or empty responses. Ensure the authenticator ID is correct and provided.
• Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify the API key configuration.
• Network or connectivity issues: Failures to reach the API endpoint may occur if the environment or base URL is misconfigured.
• Unexpected response structure: Changes in the external API schema might cause parsing issues; ensure the node version matches the API version.
• Request tracing headers: Incorrect usage of request-id or correlation-id headers won't break functionality but may affect debugging capabilities.

Links and References

• Straddle API Documentation (hypothetical link)
• n8n documentation on HTTP Request Node for understanding how headers and authentication are handled.
• General best practices for API authentication and request tracing.