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 information related to medical appointments and other healthcare-related resources. Specifically, for the Agendamento (Appointments) resource and the Listar Status De Agendamentos (List Appointment Statuses) operation, it fetches a list of possible statuses that an appointment can have within the Feegow system.
This functionality is useful in scenarios where you want to:
- Display or process all possible appointment statuses in your workflow.
- Filter or validate appointment data based on status.
- Synchronize appointment status options from Feegow into another system.
Example use case:
A clinic automation workflow could use this node to retrieve all appointment statuses and then update patient records or trigger notifications depending on the current status of their appointments.
Properties
| Name | Meaning |
|---|---|
| Filtros | Collection of filters to control the query results: |
| - Limite (limit) | Maximum number of appointment statuses to return (default 50). Must be at least 1. |
| - Offset (offset) | Number of records to skip before starting to collect the result set (optional). |
Output
The node outputs an array of JSON objects, each representing an appointment status retrieved from the Feegow API endpoint /api/appoints/status. The structure of each object depends on the API response but typically includes fields describing the status ID, name, and possibly additional metadata about the appointment status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Feegow Clinic API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The node uses HTTP requests internally to communicate with Feegow endpoints.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Network connectivity problems may prevent reaching the Feegow API.
- Providing invalid filter values (e.g., negative limit) might cause API errors.
Error messages:
Erro na operação listAppointmentStatuses para appointments: <error message>indicates a failure during the API call for listing appointment statuses. Check the API credentials, network connection, and input parameters.- If the node returns empty results unexpectedly, verify that the Feegow account has appointment statuses defined and accessible.
Links and References
- Feegow Clinic API Documentation (official API docs, if publicly available)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics
- General info on managing appointments in healthcare systems