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 dental office data. Specifically, for the Dentista (Dentist) resource and the Obter (Get) operation, it retrieves detailed information about a specific dentist by their unique ID.

Common scenarios where this node is beneficial include:

  • Fetching dentist details to display or process in workflows.
  • Integrating dentist data into other systems or reports.
  • Validating dentist existence before scheduling or assigning tasks.

Practical example:

  • A workflow that receives a dentist ID from an appointment booking system and uses this node to fetch the dentist's full profile for confirmation or further processing.

Properties

Name Meaning
ID do Dentista Unique identifier of the dentist

Output

The output JSON contains the detailed data of the requested dentist as returned by the Dental Office Cloud API. This typically includes fields such as name, CPF (taxpayer registry), RG (identity document), birth date, professional registration details (CR type, number, UF), addresses, contacts, and other relevant dentist attributes.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": 123,
  "name": "Dr. João Silva",
  "cpf": "000.000.000-00",
  "rg": "MG-12.345.678",
  "birth_date": "1980-01-01",
  "cr_type": "CRO",
  "cr_number": "12345",
  "cr_uf": "MG",
  "addresses_attributes": [...],
  "contacts_attributes": [...],
  ...
}

Dependencies

  • Requires connection to the Dental Office Cloud API.
  • Needs an API authentication credential configured in n8n (an API key or token).
  • The node uses the /v1/dentists/{id} endpoint to fetch dentist data.

Troubleshooting

  • Invalid or missing ID: If the provided dentist ID is invalid or not found, the API will likely return an error. Ensure the ID is correct and exists in the system.
  • Authentication errors: If the API credentials are incorrect or expired, requests will fail. Verify and update the API authentication token.
  • JSON parsing errors: Although not typical for the get operation, other operations involving JSON input may throw errors if JSON is malformed.
  • Network issues: Connectivity problems can cause request failures; check network access to the Dental Office Cloud API.

Common error messages:

  • "Operation 'get' not supported for dentist": Indicates an unsupported operation was requested; ensure the operation is set to "Obter" (get).
  • "Formato JSON inválido para ...": Means invalid JSON format was provided in some input field (not applicable for get but relevant for create/update).

Links and References

Discussion