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 medical appointments and related resources. Specifically, for the "Agendamento" (Appointments) resource and the "Criar Novo Agendamento" (Create New Appointment) operation, it allows users to create new appointment records by specifying details such as date, time, patient, professional, unit, and optionally a procedure.
Common scenarios where this node is beneficial include:
- Automating appointment scheduling workflows in healthcare clinics.
- Integrating appointment creation into broader patient management or CRM systems.
- Synchronizing external booking systems with Feegow Clinic's scheduling system.
For example, a clinic could use this node to automatically create an appointment when a patient books through an online portal, ensuring all relevant data is sent to Feegow's system without manual entry.
Properties
| Name | Meaning |
|---|---|
| Data | Date of the appointment in format YYYY-MM-DD (required). |
| Hora | Time of the appointment in format HH:MM (required). |
| Paciente ID | ID of the patient for whom the appointment is being created (required). |
| Procedimento ID | ID of the procedure associated with the appointment (optional). |
| Profissional ID | ID of the professional who will attend the appointment (required). |
| Unidade ID | ID of the unit/location where the appointment will take place (required). |
These properties are grouped under "Dados Do Agendamento" (Appointment Data) and must be provided when creating a new appointment.
Output
The node outputs a JSON object representing the response from the Feegow API after attempting to create the appointment. This typically includes confirmation details about the newly created appointment, such as its unique ID and any other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Feegow Clinic API via an API key credential configured in n8n.
- The node uses HTTP requests to communicate with Feegow endpoints; thus, network connectivity to the Feegow API is necessary.
- No additional external dependencies beyond the Feegow API and n8n's credential configuration.
Troubleshooting
- Missing Required Fields: If required fields like date, time, patient ID, professional ID, or unit ID are missing or invalid, the API may return errors. Ensure all mandatory fields are correctly filled.
- Invalid IDs: Using non-existent patient, professional, procedure, or unit IDs will cause the API to reject the request. Verify IDs before submission.
- API Authentication Errors: If the API key credential is not set up properly or has expired, authentication errors will occur. Check and update credentials as needed.
- Network Issues: Connectivity problems can prevent successful API calls. Confirm network access to Feegow's API endpoints.
- Error Messages: The node throws errors prefixed with
Erro na operação Criar Novo Agendamento para appointments:followed by the API error message. Use this information to diagnose issues.
Links and References
- Feegow Clinic API Documentation (Note: link is illustrative; please refer to official Feegow documentation for accurate URLs.)
- n8n Documentation on HTTP Request Node for understanding underlying request mechanics.
- General best practices for API Authentication