Actions26
Overview
This node integrates with the Dental Office Cloud API to manage users within a dental office system. Specifically, the "Usuário" (User) resource's "Atualizar" (Update) operation allows updating existing user records by sending modified user data to the API.
Common scenarios for this node include:
- Updating user contact information or email addresses.
- Changing the user's group or role within the dental office system (e.g., Administrator, Attendant, Dentist).
- Modifying the clinics associated with a user.
- Adjusting user contacts stored as JSON attributes.
Practical example: A dental office administrator wants to update a dentist's email and assign them to additional clinics. This node can be used to send those updates seamlessly to the Dental Office Cloud backend.
Properties
| Name | Meaning |
|---|---|
| IDs das Clínicas | Comma-separated list of clinic IDs to associate with the user (e.g., "1,2,3"). |
| Contatos | User contact attributes in JSON format. |
| ID do Usuário | Unique numeric identifier of the user to update (required). |
| Nome | Full name of the user. |
| User's email address. | |
| Grupo de Usuário | User group/role; options are: Administrator, Attendant, Dentist. |
Output
The node outputs the JSON response returned from the Dental Office Cloud API after updating the user. This typically includes the updated user object with all its properties as stored on the server.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the Dental Office Cloud API.
- The node uses the
dentalOfficeApiRequesthelper function to perform HTTP requests. - Proper permissions on the API side are necessary to update user data.
Troubleshooting
- Invalid JSON Format: If the "Contatos" property contains invalid JSON, the node throws an error indicating "Formato JSON inválido para contactsAttributes". Ensure the JSON is well-formed.
- Missing Required Fields: The "ID do Usuário" is mandatory. Omitting it will cause the request to fail.
- API Errors: Errors returned from the Dental Office API (e.g., unauthorized, not found) will propagate as node errors. Verify API credentials and that the user ID exists.
- Clinic IDs Parsing: Clinic IDs must be comma-separated numbers. Incorrect formatting may cause parsing errors or unexpected behavior.
Links and References
- Dental Office Cloud API documentation (not provided here, but recommended to consult for detailed API specs).
- n8n documentation on creating and using custom nodes and credentials.