Actions19
Overview
This node interacts with the Orgo API, a multi-tenant SaaS platform for organizations, to perform operations on various resources including users, contacts, events, event registrations, contract users, and payments. Specifically, for the Contract User - Get operation, it retrieves detailed information about a contract user by their ID.
Common scenarios where this node is beneficial include:
- Fetching contract user details to verify contract status or signature timestamps.
- Integrating contract user data into workflows for compliance or record-keeping.
- Automating retrieval of contract user information as part of larger organizational processes.
Example: You want to automatically fetch contract user details when a new contract is signed to update your CRM or notify relevant teams.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the contract user resource to retrieve. This is required to specify which contract user to get. |
Output
The output is a JSON object representing the contract user data retrieved from the Orgo API. For the "Get" operation on Contract User, the structure includes fields such as:
id: The contract user ID.userId: The ID of the associated user.contractId: The ID of the related contract.status: The current status of the contract user.signedAt: Timestamp when the contract was signed.createdAt: Timestamp when the contract user record was created.
The node returns this data wrapped in an array of items, each with a json property containing the contract user information.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Orgo API.
- The base URL and API token must be configured in the node credentials.
- The node uses HTTP requests to communicate with the Orgo REST API endpoints.
Troubleshooting
- Missing or invalid ID: If the ID parameter is empty or invalid, the API call will fail. Ensure the ID is correctly provided.
- Authentication errors: If the API token is missing or incorrect, the request will be unauthorized. Verify the API token in credentials.
- 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 return errors if limits are exceeded or internal errors occur. Review error messages and retry accordingly.
Common error message example:
"User ID is required but not provided"— indicates the mandatory ID parameter was not set.
Links and References
- Orgo API Documentation (hypothetical link)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/