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 organizations, to manage contract users and their associated contracts. Specifically, the Contract User - Get Many operation retrieves multiple contract user records from the Orgo system.

Typical use cases include:

  • Fetching a list of users who have signed or are associated with contracts.
  • Retrieving contract user data in either a simplified form (key fields only) or raw form (all available data).
  • Integrating contract user information into workflows for reporting, auditing, or further processing.

For example, an HR automation workflow might use this node to pull all contract users to verify contract statuses or generate reports on signed contracts.

Properties

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

Output

The node outputs an array of JSON objects representing contract users.

  • When Output is set to Simplified, each object contains these key fields:

    • id: The unique identifier of the contract user record.
    • userId: The ID of the user associated with the contract.
    • contractId: The ID of the contract.
    • status: The current status of the contract user (e.g., active, pending).
    • signedAt: Timestamp when the contract was signed.
    • createdAt: Timestamp when the record was created.

  • When Output is set to Raw, the full data structure returned by the Orgo API is passed through without filtering.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Orgo API.
  • The node expects the base URL and API token to be configured in the credentials.
  • HTTP requests are made to endpoints under /contract_users on the Orgo API.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication failures.
    • Exceeding the limit parameter or providing invalid values may result in errors or truncated results.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • "User ID is required but not provided" — Not applicable here but similar errors may occur if required parameters are missing.
    • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or resource issues.

  • Resolutions:

    • Verify that the API token and base URL are correctly set in the node credentials.
    • Ensure the limit parameter is a positive integer.
    • Check network access to the Orgo API endpoint.
    • Use the "Raw" output option to inspect full API responses for debugging.

Links and References

Discussion