Actions26
Overview
This node integrates with the Dental Office Cloud API to manage dental office data. Specifically, for the Dentista (Dentist) resource and the Remover (Delete) operation, it allows users to delete a dentist record by specifying the unique dentist ID.
Common scenarios where this node is beneficial include:
- Automating the removal of dentist records when they leave a clinic.
- Cleaning up outdated or incorrect dentist entries in bulk workflows.
- Integrating with other systems to synchronize dentist data deletions.
Example use case:
- A workflow that triggers when a dentist's contract ends, automatically removing their profile from the Dental Office system by passing their unique ID to this node.
Properties
| Name | Meaning |
|---|---|
| ID do Dentista | Unique numeric identifier of the dentist to be deleted |
Output
The node outputs JSON data representing the response from the Dental Office API after attempting to delete the specified dentist. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data output is produced by this operation.
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
/v1/dentists/{id}DELETE endpoint of the Dental Office API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent dentist ID will likely result in an error from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the Dental Office API.
Error messages:
- Errors indicating "dentist not found" suggest the ID does not exist; verify the ID before retrying.
- Authentication errors mean the API key or token is missing or invalid; check credential setup.
- JSON parsing errors are unlikely here since no complex JSON input is required for deletion.
Links and References
- Dental Office Cloud API documentation (for dentists endpoint): [Link not provided in source]
- n8n documentation on creating custom nodes and using API credentials: https://docs.n8n.io/
Note: Internal credential names and implementation details have been generalized as per instructions.