Actions5
Overview
This node integrates with the Tidi scheduling platform, enabling users to perform various operations related to appointment management. Specifically, the "Agendar Horário" (Schedule Appointment) operation allows booking an appointment by specifying details such as date, time, professional, services, and client information.
Common scenarios where this node is beneficial include:
- Automating appointment bookings in a business workflow.
- Integrating scheduling capabilities into CRM or customer support systems.
- Synchronizing appointments between Tidi and other platforms.
Practical example: Automatically schedule a client appointment for a haircut service with a specific professional on a chosen date and time, sending confirmation details downstream in the workflow.
Properties
| Name | Meaning |
|---|---|
| Idioma | Language for the request; options: Português (pt), Inglês (en) |
| Dia | Date of the appointment in format YYYY-MM-DD |
| Hora | Time of the appointment in format HH:mm |
| ID Do Profissional | ID of the professional for whom the appointment is being scheduled |
| Serviços | JSON array string containing IDs of the services to be booked |
| Nome | Client's name |
| Client's email address | |
| Telefone | Client's phone number |
Output
The node outputs a JSON object with the following structure:
{
"operation": "schedule",
"success": true,
"data": { /* response data from Tidi API */ },
"metadata": {
"endpoint": "/{language}/integration/partner/schedule",
"method": "POST",
"timestamp": "ISO 8601 timestamp"
}
}
operation: The operation performed ("schedule").success: Boolean indicating if the operation was successful.data: Contains the response from the Tidi API, typically including details about the scheduled appointment.metadata: Includes endpoint path, HTTP method used, and timestamp of the request.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Tidi platform.
- The node makes HTTP requests to the Tidi API endpoint at
https://api.tidi.com.br. - No additional environment variables are required beyond the API key credential.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrectly formatted date (
Dia) or time (Hora) strings may result in API errors. - Malformed JSON string in
Serviçosproperty can cause request failures. - Missing required fields like professional ID or client contact info may lead to incomplete bookings.
Error messages:
- Errors returned from the API are included in the node's output under
erroranderrorData. - If the node throws a
NodeOperationErrormentioning unknown operation, verify that the operation parameter is set correctly. - For HTTP errors, check the detailed message and response body provided in the error output to diagnose issues.
- Errors returned from the API are included in the node's output under
Resolution tips:
- Ensure all required properties are filled with valid values.
- Validate JSON arrays before inputting them into the
Serviçosfield. - Confirm the API key is correct and has necessary permissions.
- Use the node’s "continue on fail" option to handle errors gracefully in workflows.
Links and References
- Tidi Scheduling Platform (official site)
- Tidi API Documentation (assumed, check with provider)
- n8n HTTP Request Node documentation for understanding request configurations: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/