Actions7
- Agenda Actions
- Contact Actions
Overview
This node integrates with the MedX65 medical system API to retrieve agenda entries filtered by sector within a specified date range. It is useful for scenarios where users need to view or analyze scheduled appointments, tasks, or events grouped by specific sectors (e.g., departments or units) in a healthcare environment.
Practical examples include:
- Fetching all agenda entries for the "Radiology" sector between two dates to prepare daily schedules.
- Retrieving agenda data for a particular sector to generate reports or monitor workload distribution.
Properties
| Name | Meaning |
|---|---|
| Start Date | The start date and time to filter agenda entries from (required). |
| End Date | The end date and time to filter agenda entries up to (required). |
| Sector | The name of the sector to filter agenda entries by (required). |
Output
The node outputs an array of JSON objects representing agenda entries matching the specified sector and date range. Each object corresponds to an agenda entry as returned by the MedX65 API's GetAgendabySetor endpoint.
The exact structure of each agenda entry depends on the MedX65 API response but typically includes details such as user ID, start and end times, description, status, and linked patient 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 hosted at
https://medx65-v65teste.azurewebsites.net. - Proper configuration of the API token credential is necessary for authorization.
Troubleshooting
Common issues:
- Invalid or expired API token may cause authorization failures.
- Incorrect date formats or missing required parameters (
startDate,endDate,sector) will result in errors. - Network connectivity problems can prevent successful API calls.
Error messages:
- Authorization errors typically indicate invalid or missing API credentials; verify and update the API token.
- Validation errors about missing parameters require ensuring all required fields are filled correctly.
- If the node returns an error object, enabling "Continue On Fail" allows processing subsequent items without stopping the workflow.
Links and References
- MedX65 API Documentation (Not provided in source, placeholder for actual API docs)
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)