Actions26
Overview
The node integrates with the Dental Office Cloud API to manage scheduling (Agendamento) operations within a dental clinic environment. Specifically, the "Obter" (Get) operation under the "Agendamento" (Schedule) resource retrieves detailed information about a specific appointment by its unique ID and associated clinic ID.
This node is beneficial in scenarios where users need to fetch existing appointment details for viewing, processing, or further automation workflows such as reminders, rescheduling, or reporting. For example, a dental office might use this node to automatically retrieve appointment data when confirming bookings or preparing patient visit summaries.
Properties
| Name | Meaning |
|---|---|
| ID da Clínica | The unique numeric identifier of the clinic where the appointment is scheduled. |
| ID do Agendamento | The unique numeric identifier of the appointment to be retrieved. |
Output
The output JSON contains the detailed data of the requested appointment fetched from the Dental Office Cloud API. This typically includes all relevant fields describing the schedule such as date/time, involved dentist(s), patient, chair, status, and any additional metadata related to the appointment.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Dental Office Cloud API.
- The node depends on the
dentalOfficeApiRequesthelper function to perform HTTP requests to the API endpoints. - Proper configuration of the API credentials in n8n is necessary for successful communication.
Troubleshooting
Common Issues:
- Missing or incorrect clinic ID or appointment ID parameters will cause the API request to fail.
- Invalid or expired API authentication token can result in authorization errors.
- Network connectivity issues may prevent reaching the Dental Office Cloud API.
Error Messages:
"Operação "get" não suportada para agendamento": Indicates an unsupported operation was requested; ensure the operation name is correct.- JSON parsing errors are unlikely here since no JSON input is parsed for this operation.
- API errors returned from the Dental Office Cloud API should be checked for details like invalid IDs or permission issues.
Resolution Tips:
- Verify that both Clinic ID and Appointment ID are correctly provided and correspond to existing records.
- Confirm that the API credentials are valid and have sufficient permissions.
- Check network access and proxy settings if applicable.
Links and References
- Dental Office Cloud API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.