Orgo icon

Orgo

Interact with Orgo API - Multi-tenant SaaS platform for organizations

Actions19

Overview

This node integrates with the Orgo API, a multi-tenant SaaS platform for managing organizational data. Specifically, the "User" resource with the "Get Many" operation allows you to retrieve multiple user records from the Orgo system.

Typical use cases include:

  • Fetching a list of users (members) in an organization for reporting or synchronization.
  • Retrieving simplified user data for display in dashboards or further processing.
  • Obtaining raw detailed user data when full user profiles are needed.

For example, you might use this node to get up to 50 users with their key details (ID, email, first name, last name, status, creation date) to populate a CRM or mailing list.

Properties

Name Meaning
Output Choose between:
- Simplified: Returns only key fields (id, email, firstName, lastName, status, createdAt).
- Raw: Returns all available user data as provided by the API.
Limit Maximum number of user records to return. Must be at least 1. Default is 50.

Output

The node outputs an array of JSON objects representing users.

  • If Output is set to Simplified, each user object includes these fields:

    • id: User identifier
    • email: User's email address
    • firstName: User's first name
    • lastName: User's last name
    • status: User's status code
    • createdAt: Timestamp of user creation

  • If Output is set to Raw, the entire user object as returned by the Orgo API is included without filtering.

The output does not include binary data.

Example simplified output item:

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

Dependencies

  • Requires an API token credential for authenticating with 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 endpoints like /users?limit=....

Troubleshooting

  • Empty or missing results: Ensure the API token and base URL are correctly configured and that the limit parameter is set appropriately.
  • Authentication errors: Verify that the API token credential is valid and has sufficient permissions.
  • Invalid limit values: The limit must be a positive integer; setting it below 1 may cause errors.
  • API rate limits or network issues: These can cause request failures; check connectivity and API usage quotas.
  • Unexpected response format: If the API changes, the node’s simplified mapping may fail; consider using the Raw output option to inspect full data.

Links and References

Discussion