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 organizations. Specifically, the "Contact" resource with the "Get" operation allows users to retrieve detailed information about a single contact by its unique ID.

Typical use cases include:

  • Fetching contact details to enrich workflows with up-to-date contact information.
  • Automating CRM processes by retrieving contacts before performing further actions.
  • Integrating contact data into other systems or reports.

For example, you might use this node to get a contact's full profile when processing an incoming lead or to verify contact information before sending communications.

Properties

Name Meaning
ID The unique identifier of the contact to retrieve. This is a required string input.

Output

The output is a JSON object representing the contact retrieved from the Orgo API. It contains all available fields returned by the API for that contact, such as name, email, notes, creation date, and any other metadata associated with the contact.

If multiple contacts were retrieved (not applicable here since this is a single "Get" operation), the output would be an array of such objects. No binary data is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "name": "string",
  "email": "string",
  "notes": "string",
  "createdAt": "string"
}

Dependencies

  • Requires an API key credential for authenticating with the Orgo API.
  • The node uses the base URL and API token from the configured credentials.
  • HTTP requests are made to the Orgo API endpoints.

Troubleshooting

  • Missing or invalid ID: If the ID parameter is empty or incorrect, the API will likely return an error or no data. Ensure the ID is correctly provided.
  • Authentication errors: If the API token is missing or invalid, requests will fail with authentication errors. Verify the API key credential configuration.
  • Network issues: Connectivity problems can cause request failures. Check network access to the Orgo API endpoint.
  • API rate limits or server errors: The Orgo API may throttle requests or return server errors; handle these gracefully in your workflow.

Common error messages:

  • "Contact not found": The specified ID does not exist.
  • "Unauthorized" or "Invalid API token": Authentication failure.
  • "Request failed": General network or server error.

Links and References

Discussion