Overview
This node integrates with the Tidi scheduling platform, allowing users to retrieve various types of information related to a partner account. Specifically, for the "Obter Informações Do Parceiro" (Get Partner Information) operation, it fetches general details about the partner from the Tidi API.
Common scenarios where this node is beneficial include:
- Automatically retrieving partner profile data to synchronize with other systems.
- Displaying partner information in dashboards or reports.
- Using partner details as part of workflow decision-making or further API calls.
Practical example:
- A user wants to get the current partner's name, contact info, and settings from Tidi to update their CRM system automatically.
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": { /* response data from Tidi API about the partner */ },
"metadata": {
"endpoint": "/{language}/integration/partner",
"method": "GET",
"timestamp": "ISO 8601 timestamp"
}
}
operation
: The operation performed ("getPartner").success
: Boolean indicating if the request was successful.data
: Contains the partner information returned by the Tidi API.metadata
: Includes the API endpoint used, HTTP method, and timestamp of the request.
No binary data output is produced by this operation.
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 language code may result in unexpected or empty responses.
- Network connectivity problems can prevent reaching the Tidi API.
Error messages:
"Operação desconhecida: ..."
indicates an unsupported operation was selected.- HTTP errors from the API (e.g., 401 Unauthorized) suggest credential or permission issues.
- JSON parsing errors might occur if the API response format changes unexpectedly.
Resolutions:
- Verify that the API key credential is correctly set up and has proper permissions.
- Ensure the "Idioma" property is set to either "pt" or "en".
- Check network access and firewall settings to allow outbound HTTPS requests to the Tidi API.
Links and References
- Tidi Platform API Documentation (Assumed URL based on API base URL)
- n8n HTTP Request Node documentation for understanding request configurations: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/