Orgo

Overview

This node integrates with the Orgo API, a multi-tenant SaaS platform for managing organizations. Specifically, the "User" resource with the "Get" operation allows you to retrieve detailed information about a single user by their unique ID.

Common scenarios where this node is beneficial include:

• Fetching user details for verification or display in workflows.
• Integrating user data retrieval into automated processes such as onboarding or reporting.
• Using the user information to trigger conditional logic based on user attributes.

For example, you might use this node to get a user's profile before sending them a personalized email or to check their status before granting access to a service.

Properties

Output

The output is a JSON object representing the user data returned from the Orgo API. It contains all available fields for the user, such as their ID, email, first name, last name, status, creation date, and any other user-specific details provided by the API.

If multiple users were retrieved (not applicable here since this is a single "Get" operation), the output would be an array of such objects. For this operation, the output is a single JSON object wrapped inside an array item under the json key.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "user-id-string",
  "email": "user@example.com",
  "firstName": "John",
  "lastName": "Doe",
  "status": "active",
  "createdAt": "2023-01-01T12:00:00Z"
}

Dependencies

• Requires an API token credential for authenticating requests to the Orgo API.
• The base URL for the Orgo API must be configured in the node credentials.
• The node uses HTTP GET requests to fetch user data from the endpoint /users/{id}.

Troubleshooting

• Missing or empty ID: The node will throw an error if the user ID parameter is not provided or is empty. Ensure the ID is correctly set.
• Authentication errors: If the API token is invalid or missing, the request will fail. Verify that the API token credential is correctly configured.
• User not found: If the specified user ID does not exist, the API may return a 404 error. Confirm the ID is correct.
• Network issues: Connectivity problems can cause request failures. Check network access to the Orgo API endpoint.
• API changes: If the Orgo API changes its endpoints or response format, the node may need updating.

Links and References

• Orgo API Documentation (replace with actual URL)
• n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/