Feegow Clinic icon

Feegow Clinic

Integração com a API Feegow
Join our community

Actions25

Overview

This node integrates with the Feegow Clinic API to manage and retrieve information related to healthcare professionals and their accepted insurance plans. Specifically, the "Listar Convênios Aceitos" operation under the "Profissional" resource fetches a list of insurance agreements accepted by professionals.

Common scenarios where this node is beneficial include:

  • Retrieving which insurance plans a particular healthcare professional accepts.
  • Filtering professionals based on accepted insurances for appointment scheduling or patient referrals.
  • Integrating insurance acceptance data into broader healthcare management workflows.

For example, a clinic automation workflow might use this node to display all insurance plans accepted by a selected doctor before booking an appointment.

Properties

Name Meaning
Filtros Optional filters to narrow down the list of accepted insurances. No specific options defined in the current configuration, but users can add custom filter fields if supported by the API.

Output

The node outputs JSON data containing the response from the Feegow API endpoint /api/professionals/insurances. This JSON typically includes details about the insurance plans accepted by professionals, such as insurance IDs, names, and possibly additional metadata.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "insurances": [
    {
      "id": 123,
      "name": "Insurance Plan A",
      "details": { /* additional info */ }
    },
    {
      "id": 456,
      "name": "Insurance Plan B",
      "details": { /* additional info */ }
    }
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the Feegow Clinic API.
  • The node makes HTTP requests to Feegow's REST API endpoints.
  • Proper network access to Feegow's API service must be configured.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Network connectivity problems may prevent successful API calls.
    • Using unsupported or incorrect filter parameters could result in empty responses or API errors.

  • Error messages:

    • Errors are thrown with messages like Erro na operação listProfessionalInsurances para professionals: <error message>.
    • To resolve, verify API credentials, check network connectivity, and ensure filter parameters conform to API expectations.

Links and References

Discussion