StraddleInstall

Overview

This node operation retrieves detailed information about a specific organization by its unique identifier. It is useful in scenarios where you need to fetch up-to-date organizational data from an external service, such as verifying business details, integrating with CRM systems, or automating workflows that depend on organization-specific information.

For example, you might use this node to:

• Automatically pull organization profiles into your database when given an organization ID.
• Validate organization details before processing transactions or onboarding new clients.
• Enrich customer records with official business data during automated workflows.

Properties

Output

The output JSON contains the full organization object retrieved from the API. This includes comprehensive details such as:

• Metadata: Custom user-defined key-value pairs.
• Device info: IP address and user agent string related to the request.
• Address: Full address details including line1, line2, city, state, postal code, and country code.
• 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 for charges and payouts.
• Industry: Merchant category code, sector, and category.
• Support channels: Contact information such as email, phone, and URL.
• Bank details: Bank routing number, masked account number, account type, and bank name.
• Status details: Status message, reason, source, and timestamp of last status change.
• 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 for this operation.

Dependencies

• Requires an API key credential for authenticating with the external Straddle API.
• The base URL for API requests depends on the configured environment credential parameter.
• The node sends and expects JSON-formatted data.
• Optional headers request-id and correlation-id can be set for tracing requests.

Troubleshooting

• Missing or invalid Organization Id: The operation requires a valid organization ID; ensure it is provided and correctly formatted.
• Authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
• Network or connectivity issues: Check network access to the API endpoint and correct environment configuration.
• Unexpected response structure: If the API changes, the node’s schema may become outdated; verify compatibility with the current API version.
• Header injection issues: When using Request Id or Correlation Id, ensure values are strings and properly set to avoid malformed headers.

Links and References

• Straddle API Documentation (hypothetical link)
• n8n documentation on HTTP Request Node for understanding how headers and authentication work in API calls.