Feegow ClinicInstall

Overview

This node integrates with the Feegow Clinic API to manage and retrieve information related to medical procedures. Specifically, the "Listar Procedimentos" operation under the "Procedimento" resource allows users to list procedures available in the system, optionally filtered by procedure name or unit ID.

Common scenarios where this node is beneficial include:

• Fetching a list of medical procedures offered at a specific clinic or unit.
• Searching for procedures by name to display options in scheduling or patient management workflows.
• Integrating procedure data into broader healthcare automation processes within n8n.

For example, a clinic might use this node to automatically retrieve all procedures available in a particular unit before creating an appointment or generating reports.

Properties

Output

The node outputs a JSON array containing the list of procedures retrieved from the Feegow API. Each item in the output corresponds to a procedure object as returned by the API, typically including details such as procedure ID, name, description, and associated metadata.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "id": 123,
    "nome": "Consulta Médica",
    "descricao": "Consulta com médico generalista",
    "unidade_id": 1,
    ...
  },
  {
    "id": 124,
    "nome": "Exame de Sangue",
    "descricao": "Coleta para exame laboratorial",
    "unidade_id": 1,
    ...
  }
]

Dependencies

• Requires an active connection to the Feegow Clinic API via an API key credential configured in n8n.
• The node uses HTTP requests to Feegow endpoints; thus, network access to the Feegow API is necessary.
• No additional external dependencies beyond the Feegow API and n8n's standard environment.

Troubleshooting

• Missing or invalid Unidade ID: Since the unit ID is required, omitting it or providing an invalid value may cause the API to return errors or empty results. Ensure the unit ID is correct and provided.
• API authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate. Verify the API credentials in n8n settings.
• Network issues: Connectivity problems between n8n and the Feegow API can cause timeouts or failures. Check network configurations and firewall rules.
• Error messages: Errors thrown during execution include the operation and resource names for easier debugging, e.g., Erro na operação listProcedures para procedures: <error message>. Review the error message for specifics and verify input parameters.

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 n8n Custom Node Development Guide