Actions26
Overview
The node integrates with the Dental Office Cloud API to manage dental office resources. Specifically, for the resource Cadeira (Chair) and operation Obter (Get), it retrieves detailed information about a specific chair located in a given clinic. This is useful in scenarios where you need to fetch the current configuration or status of a particular dental chair within a clinic, for example, to display its details in a dashboard or to verify its availability before scheduling.
Practical examples:
- Fetching chair details by ID to confirm its location or name.
- Integrating chair data into appointment scheduling workflows.
- Auditing or reporting on clinic equipment.
Properties
| Name | Meaning |
|---|---|
| ID da Clínica | The unique numeric identifier of the clinic where the chair is located. |
| ID da Cadeira | The unique numeric identifier of the chair to retrieve information about. |
Output
The output JSON contains the detailed data of the requested chair as returned by the Dental Office Cloud API. This typically includes properties such as the chair's name, ID, and possibly other metadata related to the chair within the clinic.
No binary data output is involved in this operation.
Example output structure (simplified):
{
"id": 123,
"name": "Chair A",
"clinic_id": 45,
// ... other chair-specific fields
}
Dependencies
- Requires an active connection to the Dental Office Cloud API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The node uses the
/v1/clinics/{clinicId}/chairs/{id}endpoint to fetch chair details.
Troubleshooting
Common issues:
- Invalid or missing
clinicIdoridparameters will cause the API request to fail. - Network connectivity problems can prevent successful API calls.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Invalid or missing
Error messages:
"Operation "get" not supported for chair": Indicates an unsupported operation was requested; ensure the operation is correctly set to "get".- API error responses such as 404 Not Found if the chair or clinic ID does not exist.
- JSON parsing errors are unlikely here since no JSON input is parsed for this operation.
Resolutions:
- Verify that both
clinicIdandidare provided and correspond to existing entities. - Check API credentials and permissions.
- Ensure network access to the Dental Office Cloud API endpoint.
- Verify that both
Links and References
- Dental Office Cloud API documentation (general reference): Dental Office API Docs (replace with actual URL)
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/
- JSON format guidelines for input properties: https://www.json.org/json-en.html