Actions26
Overview
This node integrates with the Dental Office Cloud API to update patient (Paciente) records. It allows users to modify various details of an existing patient, such as their name, birth date, gender, current situation, specialty, and associated addresses, contacts, and documents.
Common scenarios where this node is beneficial include:
- Keeping patient information up-to-date in a dental clinic management system.
- Automating updates to patient records based on external data sources or workflows.
- Synchronizing patient data between different systems.
For example, a dental clinic could use this node to automatically update a patient's contact information or treatment status after a consultation.
Properties
| Name | Meaning |
|---|---|
| ID do Paciente | Unique identifier of the patient to update (required). |
| Nome | Full name of the patient. |
| ID da Clínica | Clinic ID associated with the patient (used for filtering or updating). |
| Data de Nascimento | Patient's birth date. |
| Gênero | Patient's gender; options: Masculino (0), Feminino (1). |
| Situação do Paciente | Current situation/status of the patient; options: 1ª Consulta, Em Tratamento, Tratamento Concluído, Alta, Abandono. |
| Especialidade | Specialty of the patient's treatment; options: Cirurgia, Endodontia, Ortodontia, Periodontia, Prótese, Implantodontia. |
| Endereços | JSON attributes representing patient's addresses. |
| Contatos | JSON attributes representing patient's contacts. |
| Documentos | JSON attributes representing patient's documents. |
Output
The node outputs the updated patient data as JSON. The structure corresponds to the response from the Dental Office Cloud API after successfully updating the patient record. It typically includes all patient fields, reflecting the new state after the update.
No binary data output is produced by this operation.
Dependencies
- Requires connection to the Dental Office Cloud API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node uses a helper function to make HTTP requests to the API endpoints.
Troubleshooting
- Invalid JSON Format: If the JSON input for addresses, contacts, or documents is malformed, the node throws an error indicating invalid JSON format. Ensure these inputs are valid JSON strings.
- Missing Required Fields: The patient ID is mandatory for the update operation. Omitting it will cause an error.
- API Errors: Errors returned by the Dental Office Cloud API (e.g., unauthorized, not found) will be propagated. Verify API credentials and that the patient ID exists.
- Incorrect Option Values: For fields like gender, situation, and specialty, ensure the values correspond exactly to the allowed options.
Links and References
- Dental Office Cloud API documentation (not provided here, but recommended to consult for detailed API behavior).
- n8n documentation on creating and using custom nodes and handling JSON inputs.