Gestor Clientes Max - Agendamento
Overview
This node manages appointments through an external scheduling API. It supports creating, retrieving, updating, and deleting appointment records. This is useful for automating calendar management, integrating booking systems, or synchronizing appointment data between platforms.
For example, you can:
- Automatically create new appointments when a form is submitted.
- Retrieve details of a specific appointment by its ID.
- Update appointment information such as time or status.
- Delete appointments that are canceled or no longer needed.
Properties
| Name | Meaning |
|---|---|
| Appointment ID | The unique numeric identifier of the appointment to get, update, or delete. |
Output
The node outputs JSON objects representing the appointment data returned from the API. For the delete operation, the output typically confirms the deletion result. The structure depends on the API response but generally includes appointment details such as title, start/end times, status, priority, client ID, and consultation price.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate requests to the external scheduling service.
- The node makes HTTP requests to the configured base URL of the scheduling API.
- Proper configuration of the API credentials in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing Appointment ID when performing get, update, or delete operations will cause errors.
- Incorrect or expired API key will result in authentication failures.
- Network connectivity problems may prevent communication with the API endpoint.
Error messages:
"Unknown operation: <operation>"indicates an unsupported operation was requested; verify the operation parameter.- API error responses (e.g., 404 Not Found) usually mean the specified appointment does not exist.
- Authentication errors suggest checking the API key credential setup.
To resolve these, ensure all required parameters are provided, credentials are valid, and the API endpoint is reachable.
Links and References
- Refer to the external scheduling API documentation for detailed information on appointment fields and supported operations.
- n8n documentation on HTTP Request node and credential management for setting up API keys.