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 - Update operation allows users to update existing contact records in the Orgo system. This is useful when you need to modify contact details such as their first name, last name, email, or notes.

Typical use cases include:

  • Keeping contact information up-to-date after receiving new data.
  • Correcting errors in contact records.
  • Adding additional notes or details to an existing contact.

For example, you might use this node to update a contact’s email address and add notes about recent interactions.

Properties

Name Meaning
ID The unique identifier of the contact to update (required).
First Name The updated first name of the contact (required).
Last Name The updated last name of the contact (required).
Additional Fields Optional extra fields to update:
• Email — The contact's email address.
• Notes — Additional notes about the contact.

Output

The node outputs the updated contact data as JSON. The structure corresponds to the response from the Orgo API PATCH /contacts/{id} endpoint and typically includes fields like:

  • id: Contact ID
  • name: Full name (concatenation of first and last names)
  • email: Updated email address (if provided)
  • notes: Updated notes (if provided)
  • Other metadata fields returned by the API

The output is always JSON; no binary data is produced.

Dependencies

  • Requires an active connection to the Orgo API.
  • Needs an API token credential configured in n8n to authenticate requests.
  • The base URL for the Orgo API must be set in the credentials.

Troubleshooting

  • Missing or invalid ID: The "ID" property is required. If omitted or incorrect, the API will return an error indicating the contact was not found.
  • Invalid or missing API token: Authentication failures will occur if the API token is not set or invalid.
  • Validation errors: The API may reject updates if required fields are missing or if field formats are invalid (e.g., malformed email).
  • Network issues: Connectivity problems can cause request failures.

To resolve these:

  • Ensure the "ID" is correct and corresponds to an existing contact.
  • Verify that the API token credential is properly configured and has sufficient permissions.
  • Double-check input values for correctness.
  • Confirm network connectivity to the Orgo API endpoint.

Links and References

Discussion