Actions26
Overview
This node integrates with the Dental Office Cloud API to update dentist records. It allows users to modify details of an existing dentist, such as personal information, professional registration data, addresses, and contacts. This operation is useful in scenarios where a dental practice needs to keep their dentist database current, for example, when a dentist changes their contact information or updates their professional credentials.
Practical examples include:
- Updating a dentist’s full name or CPF (Brazilian individual taxpayer registry identification).
- Modifying the dentist’s regional council registration details (type, number, and state).
- Changing address or contact information stored as JSON attributes.
Properties
| Name | Meaning |
|---|---|
| Nome | Full name of the dentist. |
| CPF | CPF number of the dentist (Brazilian tax ID). |
| RG | RG number of the dentist (Brazilian general registry ID). |
| Data de Nascimento | Dentist's birth date. |
| Tipo de CR | Type of Regional Council (e.g., CRO - Conselho Regional de Odontologia). |
| Número do CR | Number of the Regional Council registration. |
| UF do CR | State abbreviation of the Regional Council. |
| Endereços | Address attributes in JSON format. |
| Contatos | Contact attributes in JSON format. |
| ID do Dentista | Unique numeric identifier of the dentist (required). |
Output
The output is a JSON object representing the updated dentist record as returned by the Dental Office Cloud API. The structure includes all fields that were updated or are part of the dentist resource, reflecting the current state after the update.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Dental Office Cloud API.
- An API authentication token or API key credential must be configured in n8n to authorize requests.
- The node uses HTTP methods (PUT) to send update requests to the endpoint
/v1/dentists/{id}.
Troubleshooting
- Invalid JSON Format: If the
EndereçosorContatosJSON inputs are malformed, the node will throw an error indicating invalid JSON format. Ensure these fields contain valid JSON strings. - Missing Required ID: The
ID do Dentistaproperty is mandatory. Omitting it will cause the request to fail because the API endpoint requires the dentist's unique ID. - API Errors: Errors from the Dental Office API (such as authorization failures, invalid field values, or network issues) will be surfaced by the node. Verify API credentials and input data correctness.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Dental Office Cloud API Documentation (example placeholder, replace with actual URL if available)
- n8n Documentation on HTTP Request Nodes