Gestor Clientes Max - Agendamento
Overview
This node manages appointments through an external API, allowing users to create, retrieve, update, and delete appointment records. It is useful in scenarios where scheduling and calendar management are required, such as booking consultations, managing client meetings, or organizing events.
For the Update operation specifically, the node updates an existing appointment by its ID with new details like title, description, start/end times, status, priority, associated client, and consultation price. This is beneficial when appointment details change and need to be reflected in the system without creating a new record.
Practical example:
A healthcare provider uses this node to update patient appointment details after rescheduling or changing consultation specifics, ensuring the calendar stays accurate and up-to-date.
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 a string 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 JSON data representing the updated appointment object returned from the API. This typically includes all 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 node.
Dependencies
- Requires an API key credential for authenticating requests to the external appointment management API.
- The node makes HTTP requests to the API base URL configured in the credentials.
- Proper network connectivity to the API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Appointment ID will cause the update to fail.
- Incorrect API key or expired token will result in authentication errors.
- Providing invalid date/time formats may cause request rejection.
- Omitting required fields like title, start time, or end time can lead to validation errors.
Error messages:
"Unknown operation"or"Unknown appointment operation"indicates an unsupported or misspelled operation parameter.- HTTP 401 Unauthorized suggests problems with API credentials.
- HTTP 400 Bad Request often means missing or malformed input data.
Resolutions:
- Verify that the Appointment ID exists and is correct.
- Check and update the API key credential if needed.
- Ensure all required fields are provided and correctly formatted.
- Review API documentation for valid field values and constraints.
Links and References
- Gestor Clientes Max API Documentation (Replace with actual API docs link)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General n8n Credential Setup Guide: https://docs.n8n.io/credentials/
(Note: Replace placeholder links with actual URLs if available.)