Tidi Node icon

Tidi Node

Nós oficiais da plataforma de agendamentos Tidi.

Actions5

Overview

This node integrates with the Tidi scheduling platform, allowing users to interact with partner-related data and scheduling functionalities. Specifically, for the "Obter Informações Do Parceiro" (Get Partner Information) operation, it fetches detailed information about the partner associated with the API key.

Common scenarios where this node is beneficial include:

  • Retrieving partner profile or configuration details from the Tidi platform.
  • Using partner information to customize workflows or validate integration settings.
  • Automating data synchronization between Tidi and other systems by fetching up-to-date partner data.

Practical example:

  • A user wants to automatically pull the partner's profile information in Portuguese to display on a dashboard or use it as part of a larger automation flow.

Properties

Name Meaning
Idioma Language for the request; options are: Português (pt), Inglês (en)

Output

The node outputs JSON data structured as follows:

{
  "operation": "getPartner",
  "success": true,
  "data": { /* partner information object returned by Tidi API */ },
  "metadata": {
    "endpoint": "/{language}/integration/partner",
    "method": "GET",
    "timestamp": "ISO 8601 timestamp"
  }
}
  • operation: The operation performed, here always "getPartner".
  • success: Boolean indicating if the request was successful.
  • data: Contains the partner information retrieved from the Tidi API. The exact structure depends on the API response but typically includes partner details such as name, contact info, settings, etc.
  • metadata: Provides context about the API call including endpoint used, HTTP method, 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.
  • Makes HTTP requests to the Tidi API endpoint at https://api.tidi.com.br.
  • The node expects the API key to be configured in n8n credentials prior to execution.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Incorrect language code may result in unexpected or empty responses.
    • Network connectivity problems can lead to request timeouts or failures.

  • Error messages:

    • "Operação desconhecida": Indicates an unsupported operation was requested; ensure the operation parameter is set correctly.
    • API error responses are included in the error details; check the message and response body for specifics.

  • Resolution tips:

    • Verify that the API key credential is correctly set and has necessary permissions.
    • Confirm the language property uses one of the supported values (pt or en).
    • Check network access to https://api.tidi.com.br.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

Discussion