Tidi Node icon

Tidi Node

Nós oficiais da plataforma de agendamentos Tidi.

Actions4

Overview

This node integrates with the Tidi scheduling platform, allowing users to interact with partner-related data. Specifically, the "Listar Serviços" (List Services) operation fetches all services associated with a partner account on Tidi. This is useful for scenarios where you want to retrieve and display available services for booking or management purposes.

Practical examples include:

  • Displaying a list of services in a custom dashboard.
  • Synchronizing service data with other systems.
  • Filtering services based on specific criteria before further processing.

Properties

Name Meaning
Idioma Language for the request; options are "Português" (pt) and "Inglês" (en).
Filtros Adicionais Additional filters to narrow down the list of services. Each filter consists of:
- Nome Do Campo: The field name to filter by (string).
- Valor: The value to match for the given field (string).

Output

The node outputs an array of JSON objects, each containing:

  • operation: The operation performed, here it will be "getServices".
  • success: Boolean indicating if the request was successful.
  • data: The response data from the Tidi API, which includes the list of services matching the filters.
  • metadata: Additional information about the request including:
    • endpoint: The API endpoint used.
    • method: HTTP method used (GET).
    • timestamp: ISO timestamp of when the request was made.

No binary data output is produced by this operation.

Example output snippet:

{
  "operation": "getServices",
  "success": true,
  "data": [ /* array of service objects from Tidi API */ ],
  "metadata": {
    "endpoint": "/pt/integration/partner/services",
    "method": "GET",
    "timestamp": "2024-06-01T12:00:00.000Z"
  }
}

Dependencies

  • Requires an API key credential for authenticating requests to the Tidi platform.
  • The node makes HTTP requests to the Tidi API at https://api.tidi.com.br.
  • Proper configuration of the API key credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Incorrect filter keys or values may result in empty responses or errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "Operação desconhecida: <operation>" indicates an unsupported operation was selected.
    • HTTP errors from the API (e.g., 401 Unauthorized) suggest credential or permission issues.

  • Resolutions:

    • Verify that the API key credential is correctly set up and has proper permissions.
    • Double-check filter field names and values for correctness.
    • Ensure network access to the Tidi API endpoint is not blocked.

Links and References

Discussion