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 an external appointment management API to update existing appointments. It allows users to modify details such as the title, description, start and end times, status, priority, associated client, and consultation price of an appointment. This is useful in scenarios where appointment details need to be changed after creation, for example, rescheduling a meeting, updating the appointment status (e.g., from scheduled to confirmed), or adjusting pricing information.

Practical examples:

  • Updating the time of a medical consultation when a patient requests a new slot.
  • Changing the status of an appointment to "completed" after the service is provided.
  • Modifying the priority of an appointment to highlight urgent cases.

Properties

Name Meaning
Appointment ID The unique identifier of the appointment to update (required).
Título The title or subject of the appointment (required).
Descrição A textual description providing additional details about the appointment (optional).
Data/Hora Início The starting date and time of the appointment (required).
Data/Hora Fim The ending date and time of the appointment (required).
Status The current status of the appointment. Options: Agendado (Scheduled), Confirmado (Confirmed), Concluído (Completed), Cancelado (Cancelled). Default is Agendado.
Client ID (Opcional) Optional ID of the client associated with the appointment.
Preço da Consulta The price of the consultation in decimal format (e.g., "150.00") (optional).
Prioridade Priority level of the appointment. Options: Normal, Alta (High), Baixa (Low). Default is Normal.

Output

The node outputs a JSON object representing the updated appointment as returned by the external API. This typically includes all the appointment fields such as ID, title, description, start and end times, status, priority, client association, and consultation price.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": 123,
  "title": "Consulta médica",
  "description": "Revisão anual",
  "startTime": "2024-07-01T09:00:00Z",
  "endTime": "2024-07-01T10:00:00Z",
  "status": "confirmado",
  "priority": "alta",
  "clientId": 456,
  "consultationPrice": "150.00"
}

Dependencies

  • Requires an API key credential for authenticating with the external appointment management API.
  • The node uses HTTP requests to communicate with the API endpoint specified in the credentials.
  • Proper configuration of the API base URL and authentication token is necessary in n8n credentials settings.

Troubleshooting

  • Common issues:

    • Invalid or missing appointment ID will cause the update request to fail.
    • Incorrect API key or expired token will result in authentication errors.
    • Providing invalid date/time formats may cause the API to reject the request.
    • Omitting required fields like title, start time, or end time will lead to validation errors.

  • Error messages:

    • "Unknown operation: appointment.update": Indicates a misconfiguration or unsupported operation; ensure the operation parameter is correctly set to "update".
    • HTTP 401 Unauthorized: Check that the API key credential is valid and properly configured.
    • HTTP 400 Bad Request: Verify that all required fields are provided and formatted correctly.

  • Resolution tips:

    • Double-check the appointment ID exists before attempting an update.
    • Validate date/time inputs conform to ISO 8601 format.
    • Ensure the API key has sufficient permissions to perform updates.

Links and References

Discussion