Overview
This node integrates with the Tidi scheduling platform, enabling users to interact with partner-related data and scheduling availability. It supports operations such as retrieving partner information, listing services and professionals associated with the partner, and checking schedule availability for a professional.
Common scenarios include:
- Fetching detailed information about a partner organization.
- Listing all available services or professionals linked to a partner.
- Checking if a specific professional is available for certain services at given times.
Practical examples:
- A business automating appointment bookings can use this node to verify professional availability before confirming appointments.
- An application displaying partner details and their offered services can fetch updated data dynamically.
- A scheduling system can list professionals and services to allow users to select options when booking.
Properties
Name | Meaning |
---|---|
Idioma | Language for the request; options are "Português" (pt) and "Inglês" (en). |
Additional properties appear depending on the selected operation:
Operation (not listed in user properties but present in code):
- Options:
- "Obter Informações Do Parceiro" (getPartner)
- "Listar Serviços" (getServices)
- "Listar Profissionais" (getProfessionals)
- "Verificar Disponibilidade" (checkAvailability)
- Options:
For checkAvailability operation:
- ID Do Profissional: The professional's ID to check availability for.
- Serviços: JSON array string of service IDs to check availability against.
For getServices and getProfessionals operations:
- Filtros Adicionais: Additional filters as key-value pairs to refine the query.
Output
The node outputs an array of items where each item contains a json
object structured as follows:
{
"operation": "<operation_name>",
"success": true,
"data": <response_data_from_Tidi_API>,
"metadata": {
"endpoint": "<API_endpoint_used>",
"method": "<HTTP_method_used>",
"timestamp": "<ISO_timestamp_of_request>"
}
}
operation
: The name of the executed operation.success
: Boolean indicating if the API call was successful.data
: The raw response data returned from the Tidi API.metadata
: Contains details about the API endpoint, HTTP method, and timestamp of the request.
If an error occurs and the node is set to continue on failure, the output includes:
{
"operation": "<operation_name_or_unknown>",
"success": false,
"error": "<error_message>",
"timestamp": "<ISO_timestamp_of_error>"
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Tidi platform.
- Makes HTTP requests to the Tidi API base URL:
https://api.tidi.com.br
. - The node expects the API key to be configured in n8n credentials prior to execution.
Troubleshooting
- Unknown Operation Error: If an unsupported operation is specified, the node throws an error indicating "Operação desconhecida". Ensure the operation parameter matches one of the supported options.
- Authentication Failures: Missing or invalid API key will cause HTTP request failures. Verify that the API key credential is correctly set up.
- Invalid JSON in Services Field: For the "checkAvailability" operation, the services property must be a valid JSON array string. Malformed JSON will cause errors.
- Filter Misconfiguration: When using additional filters, ensure keys and values are properly set; empty or incorrect filters may lead to unexpected results or no data.
- Continue On Fail Behavior: If enabled, the node will output error details per item instead of stopping execution, useful for batch processing with partial failures.
Links and References
- Tidi Platform API Documentation (Assumed based on API URL, please verify actual docs)
- n8n HTTP Request Node Documentation
- n8n Custom Node Development Guide