Actions25
- Agendamento Actions
- Convênio Actions
- Empresa Actions
- Especialidade Actions
- Paciente Actions
- Procedimento Actions
- Profissional Actions
Overview
This node integrates with the Feegow Clinic API to manage and retrieve appointment data based on various filters. Specifically, the "Listar Agendamentos Por Filtros" operation allows users to list appointments filtered by date range, professional ID, and unit ID. This is useful for clinics or medical offices that want to automate fetching scheduled appointments within specific criteria, such as all appointments for a given professional during a certain period or all appointments at a particular clinic location.
Practical examples:
- Retrieve all appointments scheduled between two dates to generate daily or weekly reports.
- Filter appointments by a specific healthcare professional to monitor their schedule.
- List appointments for a particular clinic unit to manage resources or room availability.
Properties
| Name | Meaning |
|---|---|
| Data Fim (data_fim) | Optional end date filter in format YYYY-MM-DD to limit appointments up to this date. |
| Data Início (data_inicio) | Optional start date filter in format YYYY-MM-DD to limit appointments from this date onward. |
| Profissional ID (profissional_id) | Optional numeric ID of the professional to filter appointments by a specific healthcare provider. |
| Unidade ID (unidade_id) | Optional numeric ID of the unit/clinic location to filter appointments by location. |
Output
The node outputs an array of JSON objects representing the appointments matching the specified filters. Each item in the output corresponds to one appointment record returned by the Feegow API. The exact structure depends on the API response but typically includes details such as appointment date, time, patient information, professional, status, and location.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Feegow Clinic API.
- The node uses HTTP requests to communicate with the Feegow API endpoints.
- Proper configuration of the API credentials in n8n is necessary for successful operation.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrect date formats in filters may lead to API request failures.
- Providing IDs (professional or unit) that do not exist in the system will result in empty results or errors.
- Error messages:
- Errors are thrown with messages like
Erro na operação listAppointmentsByFilters para appointments: <error message>. - To resolve, verify the input parameters, especially date formats and IDs, and ensure the API credentials are valid and active.
- Errors are thrown with messages like
Links and References
- Feegow Clinic API Documentation (example link; replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- General best practices for date formatting and filtering in APIs