MedX65 icon

MedX65

Interact with MedX65 medical system API
Join our community

Actions7

Overview

This node integrates with the MedX65 medical system API to manage agenda (calendar) entries. Specifically, the "Get by User" operation retrieves agenda entries filtered by a specific user within a given date range. This is useful for scenarios where you want to fetch all scheduled appointments or events assigned to a particular user (e.g., a doctor or staff member) between two dates.

Practical examples:

  • Fetching all appointments for Dr. Smith between January 1 and January 31.
  • Retrieving a user's schedule for workload analysis or reporting.
  • Displaying a user's agenda in a custom dashboard or application.

Properties

Name Meaning
Start Date The start date/time to filter agenda entries from (inclusive).
End Date The end date/time to filter agenda entries until (inclusive).
User ID The numeric ID of the user whose agenda entries should be retrieved.

Output

The output is an array of JSON objects representing agenda entries for the specified user and date range. Each object corresponds to one agenda entry as returned by the MedX65 API endpoint /api/integration/GetAgendabyUsuario.

The exact structure of each agenda entry depends on the MedX65 API response but typically includes fields such as start time, end time, description, status, linked patient ID, and user ID.

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 hosted at https://medx65-v65teste.azurewebsites.net.
  • The integration token is used to obtain an authorized bearer token before making API calls.
  • 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 user ID resulting in empty or no results.
    • Date format errors if the input dates are not properly formatted ISO strings.
    • Network connectivity issues to the MedX65 API endpoint.

  • Error messages:

    • Authorization errors typically indicate problems with the API token; re-authenticate or refresh the token.
    • HTTP 400 or 500 errors may indicate malformed requests or server-side issues; verify input parameters.
    • If the node returns an error object in the output, check the error message for details.

  • Resolution tips:

    • Ensure the API credentials are valid and have the required permissions.
    • Double-check that the user ID exists in the MedX65 system.
    • Use valid ISO 8601 date-time strings for start and end dates.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion