Actions19
Overview
The node interacts with the Orgo API, a multi-tenant SaaS platform for managing organizations. Specifically, the "Contact" resource with the "Get Many" operation retrieves multiple contact records from the Orgo system.
This operation is useful when you want to fetch a list of contacts for further processing, reporting, or integration with other systems. For example, you might use it to synchronize your CRM contacts, generate mailing lists, or analyze contact data in bulk.
The node supports returning either simplified contact data (key fields only) or raw data (all available fields), allowing flexibility depending on the use case.
Properties
| Name | Meaning |
|---|---|
| Output | Choose between: - Simplified: Returns simplified data with key fields only (id, name, email, createdAt). - Raw: Returns all available contact data as provided by the API. |
| Limit | Maximum number of contact results to return. Must be at least 1. Defaults to 50. |
Output
The output is an array of JSON objects representing contacts.
If Output is set to Simplified, each contact object includes:
id: Unique identifier of the contact.name: Full name of the contact.email: Email address of the contact.createdAt: Timestamp when the contact was created.
If Output is set to Raw, each contact object contains all fields returned by the Orgo API for contacts, which may include additional metadata and custom fields.
The node does not output binary data.
Dependencies
- Requires an API token credential for authenticating with the Orgo API.
- The base URL for the Orgo API must be configured in the credentials.
- The node uses HTTP requests to communicate with the Orgo REST API endpoints.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Exceeding API rate limits may result in errors or throttling.
- Providing a limit value less than 1 will be rejected.
Error messages:
- Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
- Network or timeout errors suggest connectivity issues; check network access to the Orgo API endpoint.
- Unexpected response formats may occur if the API changes; ensure the node and credentials are up to date.
Links and References
- Orgo API Documentation (example placeholder, replace with actual URL if known)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/