Dental Office icon

Dental Office

Integração com a API do Dental Office Cloud

Actions26

Overview

The "Remover" operation for the "Agendamento" (Schedule) resource in this Dental Office node allows users to delete a specific appointment from a clinic's schedule. This is useful for managing and maintaining up-to-date scheduling data by removing appointments that are canceled or no longer valid.

Typical use cases include:

  • Automatically deleting appointments when patients cancel.
  • Cleaning up outdated or erroneous schedule entries.
  • Integrating with other systems to synchronize appointment deletions.

For example, if a patient cancels their dental appointment, this node operation can be used to remove that appointment from the clinic's schedule in the Dental Office Cloud system.

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 removed.

Output

The output JSON contains the response from the API after attempting to delete the specified appointment. Typically, this will be an empty object or confirmation message indicating successful deletion.

No binary data is output by this operation.

Example output JSON:

{}

Dependencies

  • Requires an active connection to the Dental Office Cloud API.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node uses the HTTP DELETE method on the endpoint /v1/clinics/{clinicId}/schedules/{id} to perform the removal.

Troubleshooting

  • Common issues:

    • Providing invalid or non-existent clinic or appointment IDs will result in errors.
    • Missing required parameters (clinicId or id) will cause the node to fail.
    • Network or authentication failures may prevent successful deletion.

  • Error messages:

    • "Operation 'delete' not supported for schedule": Indicates an incorrect operation name or resource mismatch.
    • API errors such as 404 Not Found if the appointment does not exist.
    • Authentication errors if the API key or credentials are invalid or missing.

  • Resolutions:

    • Verify that the clinic and appointment IDs are correct and exist in the system.
    • Ensure the API credential is properly set up and has necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

  • Dental Office Cloud API documentation (for schedules): /v1/clinics/{clinicId}/schedules/{id}
  • n8n documentation on creating custom nodes and using credentials.

Discussion