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, enabling automation of various healthcare-related operations. Specifically, for the Paciente (Patient) resource and the Listar Pacientes (List Patients) operation, it retrieves a list of patients from the Feegow system based on optional filters such as CPF (Brazilian individual taxpayer registry identification), patient name, and a limit on the number of results.
This node is beneficial in scenarios where you need to synchronize patient data, generate reports, or trigger workflows based on patient information stored in Feegow. For example, a clinic could use this node to fetch recent patient registrations or filter patients by name or CPF for follow-up communications.
Properties
| Name | Meaning |
|---|---|
| Filtros | Collection of optional filters to narrow down the patient list: |
| - CPF: Patient's CPF (optional) | |
| - Limite: Maximum number of patient records to return (default 50) | |
| - Nome: Patient's name (optional) |
Output
The node outputs an array of JSON objects representing patients retrieved from the Feegow API. Each item in the output corresponds to one patient record returned by the API.
- The
jsonfield contains the full response data from the API endpoint/api/patient/list. - The structure depends on the Feegow API but typically includes patient details such as ID, name, CPF, birth date, phone, and other relevant patient information.
- This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Feegow Clinic API.
- The node uses HTTP GET requests to the
/api/patient/listendpoint with optional query parameters based on the provided filters. - No additional external dependencies are required beyond the configured API authentication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing invalid filter values (e.g., malformed CPF) may result in empty responses or API errors.
- Exceeding API rate limits or network connectivity problems can cause request failures.
Error messages:
- Errors are thrown with messages like
Erro na operação listPatients para patient: <error message>. - To resolve, verify API credentials, check filter inputs, and ensure network access to the Feegow API.
- Errors are thrown with messages like
Links and References
- Feegow Clinic API Documentation (Please consult the official Feegow API docs for detailed endpoint specifications and examples.)