Dental Office

Overview

This node integrates with the Dental Office Cloud API to manage patient records. Specifically, the "Paciente" (Patient) resource with the "Remover" (Remove/Delete) operation allows users to delete a patient from the system by specifying their unique ID.

Common scenarios for this node include:

• Automating patient record cleanup when patients are no longer active.
• Integrating with other systems to synchronize patient deletions.
• Managing patient data lifecycle within dental office workflows.

Example use case: A dental office wants to automatically remove patient records from their system when they unsubscribe or request deletion, ensuring compliance with data retention policies.

Properties

Output

The output JSON contains the response from the Dental Office Cloud API after attempting to delete the specified patient. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data is output by this node.

Dependencies

• Requires an API key credential for authenticating requests to the Dental Office Cloud API.
• The node uses the dentalOfficeApiRequest helper function to perform HTTP DELETE requests to the endpoint /v1/customers/{id} where {id} is the patient ID.
• Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

• Invalid or missing patient ID: Ensure the "ID do Paciente" property is provided and corresponds to an existing patient.
• API authentication errors: Verify that the API key credential is correctly set up and has permissions to delete patients.
• JSON parsing errors: Not applicable for this operation since it only requires a numeric ID.
• Network or API errors: Check network connectivity and API status; the node throws errors if the API returns failure responses.
• If the node is set to continue on fail, errors will be included in the output JSON under an error field.

Links and References

• Dental Office Cloud API documentation (for patient management endpoints)
• n8n documentation on creating custom nodes and using credentials