Dental Office icon

Dental Office

Integração com a API do Dental Office Cloud

Actions26

Overview

This node integrates with the Dental Office Cloud API to manage user data within a dental office system. Specifically, the "Usuário" (User) resource with the "Obter" (Get) operation allows retrieving detailed information about a specific user by their unique ID.

Common scenarios where this node is beneficial include:

  • Fetching user details for display or processing in workflows.
  • Integrating user data retrieval into automated processes such as appointment scheduling or notifications.
  • Synchronizing user information between Dental Office Cloud and other systems.

Practical example:

  • A workflow that triggers when a new appointment is created and uses this node to fetch the patient's user details to personalize communications.

Properties

Name Meaning
ID do Usuário Unique numeric identifier of the user to retrieve

Output

The node outputs JSON data representing the user object retrieved from the Dental Office Cloud API. The structure typically includes all user details stored in the system, such as name, email, group affiliations, addresses, contacts, and other relevant attributes.

No binary data output is involved in this operation.

Example output JSON snippet (simplified):

{
  "id": 123,
  "name": "John Doe",
  "email": "john.doe@example.com",
  "user_group_id": 5,
  "addresses_attributes": [...],
  "contacts_attributes": [...],
  ...
}

Dependencies

  • Requires an active connection to the Dental Office Cloud API.
  • Needs an API authentication credential configured in n8n (an API key or token).
  • The node depends on the dentalOfficeApiRequest helper function to make HTTP requests to the API endpoints.

Troubleshooting

  • Invalid or missing user ID: Ensure the "ID do Usuário" property is provided and is a valid number. Missing or invalid IDs will cause the API request to fail.
  • API authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
  • Network issues: Check connectivity to the Dental Office Cloud API endpoint.
  • Unexpected API responses: If the user ID does not exist, the API may return a 404 error; handle this gracefully in your workflow or enable "Continue On Fail" to avoid stopping execution.
  • JSON parsing errors: Although not typical for the "get" operation, other operations involving JSON input fields require valid JSON format.

Links and References

Discussion