Feegow Clinic icon

Feegow Clinic

Integração com a API Feegow

Overview

This node integrates with the Feegow Clinic API to perform various operations related to healthcare management. Specifically, for the "Empresa" resource and the "Listar Locais" operation, it retrieves a list of locations (locals) associated with a company unit. This is useful for workflows that need to fetch or display physical locations tied to a healthcare provider's company structure.

Practical examples include:

  • Automatically retrieving all clinic locations before scheduling appointments.
  • Syncing location data with other systems or databases.
  • Displaying available company locations in a user interface or report.

Properties

Name Meaning
Filtros Filters to apply when listing locations. Contains:
• Unidade ID: The ID of the unit (required).

The only filter required for this operation is the "Unidade ID," which specifies the company unit whose locations you want to list.

Output

The output is a JSON object containing the response from the Feegow API endpoint /api/company/list-local. This typically includes an array of location objects related to the specified unit. Each location object may contain details such as location ID, name, address, and other relevant metadata about the local.

No binary data is output by this operation.

Example output structure (simplified):

{
  "locations": [
    {
      "id": 123,
      "name": "Main Clinic",
      "address": "123 Health St.",
      ...
    },
    {
      "id": 124,
      "name": "Downtown Branch",
      "address": "456 Wellness Ave.",
      ...
    }
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the Feegow Clinic API.
  • The node uses HTTP requests to Feegow endpoints; thus, internet connectivity and proper API access permissions are necessary.
  • No additional external libraries beyond those bundled with n8n are required.

Troubleshooting

  • Missing or invalid Unidade ID: Since "Unidade ID" is mandatory, omitting it or providing an invalid value will likely cause the API to return an error or empty results. Ensure the correct unit ID is provided.
  • API authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail with authentication errors. Verify the API key configuration.
  • Network issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.
  • Unexpected API responses: If the Feegow API changes or returns unexpected data, the node might throw errors. Review the API documentation or contact Feegow support.

Common error message format:

Erro na operação listLocals para company: <error message>

This indicates an error occurred during the "Listar Locais" operation for the "Empresa" resource, with the specific error message from the API or network layer.

Links and References


If you need further details on other resources or operations, feel free to ask!

Discussion