Dental Office icon

Dental Office

Integração com a API do Dental Office Cloud

Actions26

Overview

The node integrates with the Dental Office Cloud API to manage dental office scheduling data. Specifically, for the Agendamento (Schedule) resource and the Listar (List) operation, it retrieves a list of appointments filtered by optional parameters such as dentist ID, chair ID, and date range.

This node is useful in scenarios where you want to automate or synchronize appointment data from the Dental Office system into your workflows. For example, you can use it to:

  • Fetch all appointments for a specific dentist within a given date range.
  • Retrieve schedules assigned to a particular dental chair.
  • Aggregate appointment data for reporting or notification purposes.

Properties

Name Meaning
ID do Dentista Filter appointments by the responsible dentist's ID (number).
Data de Início Start date/time to filter appointments from (dateTime).
Data de Fim End date/time to filter appointments until (dateTime).
ID da Cadeira Filter appointments by the dental chair's ID (number).

Output

The output is an array of JSON objects representing the schedule entries retrieved from the Dental Office API. Each item corresponds to one appointment and contains fields returned by the /v1/schedules endpoint, such as appointment start time, dentist details, chair information, customer info, and status.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Dental Office Cloud API.
  • The node uses the internal helper function dentalOfficeApiRequest to perform HTTP requests.
  • Proper configuration of the API credential in n8n is necessary for successful communication.

Troubleshooting

  • Empty results: Ensure that the filter parameters (dates, dentistId, chairId) are correctly set and correspond to existing data in the Dental Office system.
  • Invalid date format errors: The start and end properties must be valid date-time values; otherwise, the API may reject the request.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • JSON parsing errors: Although not directly related to this operation, other operations in the node expect some JSON inputs; invalid JSON will cause errors.
  • Unsupported operation error: If the operation name is misspelled or unsupported for the "schedule" resource, the node throws an error indicating the operation is not supported.

Links and References

Discussion