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 operations on various resources such as contacts, agenda entries, patients, users, sectors, and integrations. Specifically, the Contact - Get by ID operation retrieves detailed information about a single contact using its unique identifier.

Typical use cases include:

  • Fetching contact details for patient management or communication.
  • Integrating contact data into workflows that require up-to-date contact information.
  • Automating retrieval of contact records for reporting or synchronization with other systems.

For example, a healthcare workflow might use this node to get a contact's full profile by their ID before scheduling an appointment or sending notifications.

Properties

Name Meaning
Contact ID The unique identifier of the contact to retrieve. This is a required string input.

Output

The node outputs JSON data representing the contact details retrieved from the MedX65 API. The structure corresponds to the contact record fields returned by the endpoint /api/integration/GetContatosById?idcontato={contactId}.

The output JSON typically includes all relevant contact information such as name, email, phone numbers, CPF/CGC number, birth date, gender, and possibly address and other metadata (depending on the API response).

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential to access the MedX65 API.
  • The node makes HTTP requests to the MedX65 API endpoints hosted at https://medx65-v65teste.azurewebsites.net.
  • The integration token is used to obtain an authorized bearer token before making resource-specific requests.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or expired API token causing authorization failures.
    • Incorrect or missing Contact ID leading to empty or error responses.
    • Network connectivity problems preventing access to the MedX65 API endpoint.

  • Error messages:

    • Authorization errors (e.g., 401 Unauthorized) indicate issues with the API token; re-authenticate or update credentials.
    • 404 Not Found may occur if the Contact ID does not exist; verify the ID correctness.
    • Request timeouts or connection errors suggest network or endpoint availability problems.

  • Resolutions:

    • Ensure the API key/token is valid and has proper permissions.
    • Double-check the Contact ID input for accuracy.
    • Confirm network access to the MedX65 API URL.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.

Links and References

Discussion