Gestor Clientes Max icon

Gestor Clientes Max

Integração completa com API de agenda para gerenciar clientes e agendamentos
Join our community

Actions14

Overview

This node integrates with the "Gestor Clientes Max" API to manage appointments, clients, and financial accounts. Specifically, for the Agendamento (Appointment) resource with the Get By Client operation, it fetches all appointments associated with a given client ID.

This is useful in scenarios where you want to retrieve all scheduled appointments for a particular client, such as in customer management systems, booking platforms, or service scheduling applications. For example, a business could use this node to pull all upcoming or past appointments of a client to display their history or prepare for an upcoming meeting.

Properties

Name Meaning
Client ID The numeric ID of the client whose appointments you want to retrieve. This is required.

Output

The output JSON contains the list of appointments associated with the specified client. Each appointment object typically includes details such as:

  • Appointment ID
  • Title
  • Description (optional)
  • Start time and end time (date-time)
  • Status (e.g., scheduled, confirmed, completed, canceled)
  • Priority (normal, high, low)
  • Associated client ID (if any)
  • Consultation price (optional)

The exact structure depends on the API response but generally reflects the appointment data stored in the Gestor Clientes Max system.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Gestor Clientes Max API.
  • The node expects the API base URL and API key to be configured in the credentials.
  • Network access to the Gestor Clientes Max API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing client ID parameter will cause the request to fail.
    • Incorrect or expired API key will result in authentication errors.
    • Network connectivity problems can prevent successful API calls.
    • If the client ID does not exist, the API may return an empty list or an error.

  • Error messages:

    • "Unknown appointment operation: getByClient": Indicates the operation name was not recognized; ensure the operation is correctly set to "Get By Client".
    • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) should be checked against the API documentation and credentials.

  • Resolution tips:

    • Verify that the client ID is correct and exists in the system.
    • Confirm that the API key credential is valid and has proper permissions.
    • Check network connectivity and firewall settings.
    • Enable "Continue On Fail" in the node settings if you want the workflow to proceed despite individual errors.

Links and References

Discussion