MedX65 icon

MedX65

Interact with MedX65 medical system API
Join our community

Actions7

Overview

This node integrates with the MedX65 medical system API to perform various operations related to medical scheduling, contacts, integrations, patients, users, and sectors. Specifically for the Contact - Search operation, it allows searching for contacts by name, CPF (a Brazilian individual taxpayer registry identification), or phone number. This is useful in scenarios where you need to quickly find contact details within the MedX65 system based on partial or full identifiers.

Practical examples include:

  • Searching for a patient or client contact by their name or phone number before creating an appointment.
  • Quickly retrieving contact information during customer support or medical administration tasks.

Properties

Name Meaning
Search Term The string used to search contacts by name, CPF, or phone number

Output

The output of the Search Contact operation is an array of JSON objects representing the contacts that match the search term. Each object contains the contact details as returned by the MedX65 API's GetContatosGridBySearch endpoint.

The exact structure depends on the API response but typically includes fields such as contact name, CPF/CGC, phone numbers, email, birth date, gender, and other contact-related information.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential for the MedX65 system.
  • The node makes HTTP requests to the MedX65 API endpoints hosted at https://medx65-v65teste.azurewebsites.net.
  • The integration token is refreshed via a dedicated API call before each request.
  • Proper configuration of the API key credential in n8n is necessary for successful authentication.

Troubleshooting

  • Common issues:

    • Invalid or expired API token: The node fetches a new authorized token before each request; if the initial integration token is invalid, authentication will fail.
    • Network connectivity problems to the MedX65 API endpoint.
    • Incorrect or empty search term leading to no results.

  • Error messages:

    • Authentication errors usually indicate issues with the provided API credentials or token expiration.
    • HTTP request failures may return status codes indicating server errors or bad requests; verify parameters and network access.
    • If the node is set to continue on failure, error details are returned in the output JSON under an error field.

Links and References

Discussion