Actions7
- Agenda Actions
- Contact Actions
Overview
This node integrates with the MedX65 medical system API to retrieve agenda entries within a specified date range. It is useful for scenarios where users need to fetch scheduled appointments or events from the MedX65 agenda, filtered by time period. For example, a healthcare administrator could use this node to pull all agenda entries between two dates to generate reports or synchronize schedules.
The "Get" operation under the "Agenda" resource specifically fetches agenda entries that fall between a user-defined start and end date.
Properties
| Name | Meaning |
|---|---|
| Start Date | The start date and time used to filter agenda entries. Only entries on or after this date are returned. |
| End Date | The end date and time used to filter agenda entries. Only entries on or before this date are returned. |
Output
The output is an array of JSON objects representing agenda entries retrieved from the MedX65 API. Each object corresponds to one or more agenda records matching the date filter criteria. The exact structure depends on the MedX65 API response but typically includes details such as appointment times, descriptions, user IDs, status, and linked patient information.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential for the MedX65 system.
- The node makes HTTP GET requests to the MedX65 API endpoint
https://medx65-v65teste.azurewebsites.net/api/integration/GetAgendawith query parameters for start and end dates. - Proper configuration of the API credential with a valid integration token is necessary.
Troubleshooting
Common issues:
- Invalid or expired API token may cause authorization failures.
- Incorrect date formats or missing required date parameters will result in errors or empty results.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authorization errors typically indicate invalid or missing API credentials; verify and update the token.
- HTTP request failures may show status codes like 400 (bad request) if parameters are malformed.
- If the node returns an error object in the output, check the message for details and ensure all required inputs are correctly set.
Links and References
- MedX65 API Documentation (if available) (Assumed URL based on endpoint)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics