Actions5
Overview
This node integrates with the Tidi appointment scheduling platform, allowing users to perform various operations such as listing services, listing professionals, checking availability, scheduling appointments, and retrieving partner information. It is useful for automating booking workflows, managing service and professional data, and verifying schedule availability directly within n8n.
A practical example is using this node to list all available services in Portuguese, filter them by specific criteria, and then schedule an appointment with a selected professional at a chosen time.
Properties
| Name | Meaning |
|---|---|
| Operação | The operation to perform. Options: "Agendar Horário" (Schedule appointment), "Listar Profissionais" (List professionals), "Listar Serviços" (List services), "Obter Informações Do Parceiro" (Get partner info), "Verificar Disponibilidade" (Check availability). |
| Idioma | Language for the request. Options: "Português" (pt), "Inglês" (en). |
| Filtros Adicionais | Additional filters for listing services or professionals. Each filter has a field name ("Nome Do Campo") and a value ("Valor") to filter results. Only shown for "Listar Serviços" and "Listar Profissionais" operations. |
| ID Do Profissional | Professional ID used for checking availability or scheduling an appointment. |
| Serviços | JSON array string of service IDs relevant for checking availability or scheduling. |
| Dia | Date of the appointment in YYYY-MM-DD format (used when scheduling). |
| Hora | Time of the appointment in HH:mm format (used when scheduling). |
| Nome | Client's name for the appointment (used when scheduling). |
| Client's email address (used when scheduling). | |
| Telefone | Client's phone number (used when scheduling). |
Output
The node outputs a JSON object containing:
operation: The operation performed.success: Boolean indicating if the operation was successful.data: The response data from the Tidi API corresponding to the requested operation.metadata: Additional metadata including:endpoint: The API endpoint called.method: HTTP method used.timestamp: ISO timestamp of the request execution.
If an error occurs and "Continue On Fail" is enabled, the output will include:
success: falseerror: Error messageerrorData: Detailed error response from the API if availabletimestamp: When the error occurred
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Tidi platform.
- Makes HTTP requests to the Tidi API endpoints at
https://api.tidi.com.br. - The node expects the API key to be configured in n8n credentials before use.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication errors.
- Incorrectly formatted JSON strings for service IDs may cause request failures.
- Using unsupported or misspelled operation names will throw an "Unknown operation" error.
- Filters without both key and value are ignored; ensure both are provided.
Error messages:
"Operação desconhecida: <operation>"indicates an invalid operation parameter.- HTTP errors from the API will be surfaced with details if available.
- If the node fails and "Continue On Fail" is disabled, it will stop execution on the first error.
Resolutions:
- Verify API key validity and permissions.
- Ensure JSON arrays for services are correctly formatted strings.
- Double-check operation names and required parameters.
- Use "Continue On Fail" cautiously depending on workflow needs.
Links and References
- Tidi Official Website (for general platform info)
- No direct public API documentation link provided in source code; consult Tidi support for API details.