Dental Office icon

Dental Office

Integração com a API do Dental Office Cloud

Overview

The node integrates with the Dental Office Cloud API to update an existing appointment (agendamento) in a dental clinic system. It allows modifying details such as the clinic ID, dentist(s) involved, patient ID, chair ID, appointment start time, description, whether the appointment is personal to the dentist, and the current status of the appointment.

This node is useful for dental office automation workflows where appointments need to be programmatically updated based on external triggers or data changes. For example, it can be used to reschedule appointments, update patient or dentist assignments, or change the appointment status after confirmation or cancellation.

Properties

Name Meaning
ID da Clínica Numeric ID of the clinic where the appointment is scheduled
ID do Dentista Numeric ID of the primary dentist responsible for the appointment
IDs dos Dentistas Comma-separated list of numeric IDs of dentists involved in the appointment (e.g., "1,2,3")
ID do Paciente Numeric ID of the patient associated with the appointment
Agendamento Pessoal Boolean indicating if the appointment is personal to the dentist
Descrição Text description or notes about the appointment
Situação do Agendamento Current status of the appointment; options include Confirmar (1), Confirmado (2), Em Atendimento (3), Atendido (4), Faltou (5), Cancelado (6)
ID da Cadeira Numeric ID of the chair where the appointment will take place
ID do Agendamento Numeric unique identifier of the appointment (required)
Data e Hora do Agendamento Date and time when the appointment starts

Output

The node outputs JSON data representing the updated appointment object returned by the Dental Office Cloud API. This typically includes all relevant fields of the appointment such as IDs, timestamps, descriptions, status, and related entities (dentists, patient, chair).

No binary data output is produced by this operation.

Dependencies

  • Requires connection to the Dental Office Cloud API.
  • Requires an API authentication credential configured in n8n to authorize requests.
  • The node uses HTTP methods (PUT) to update appointment data at endpoints structured like /v1/clinics/{clinicId}/schedules/{id}.

Troubleshooting

  • Invalid JSON format errors: Some properties accept JSON strings (not applicable here for update schedule but common in other resources). Ensure JSON inputs are well-formed.
  • Missing required parameters: The clinicId and id (appointment ID) are mandatory. Omitting these will cause errors.
  • API request failures: Errors from the API may occur due to invalid IDs, unauthorized access, or network issues. Check credentials and parameter correctness.
  • Incorrect date/time format: The scheduleStart must be a valid datetime string; otherwise, the API may reject the request.
  • Status value errors: The scheduleSituationId must be one of the predefined options; invalid values will cause errors.

Links and References

Discussion