N8N Tools - Tidio APIInstall

Overview

This node enables sending a file attachment to a specific conversation in the Tidio live chat system. It is useful for automating customer support or engagement workflows where files such as images, documents, or other media need to be shared with visitors or contacts during a chat session.

Typical use cases include:

• Sending product brochures or manuals automatically when a visitor requests them.
• Sharing screenshots or images to assist in troubleshooting.
• Delivering invoices, contracts, or other documents directly within the chat.

By integrating this node into an n8n workflow, users can programmatically send files to ongoing conversations without manual intervention, improving response efficiency and customer experience.

Properties

Output

The node outputs a JSON object representing the response from the Tidio API after attempting to send the file message. This typically includes details about the sent message such as its ID, type, content, timestamps, and status.

If the operation fails, the output JSON contains an error field with the error message.

No binary data is output by this node; it only handles sending file URLs as part of the message content.

Example output structure (simplified):

{
  "id": "message_id",
  "type": "file",
  "content": "File attachment",
  "file_url": "https://example.com/file.pdf",
  "created_at": "2024-01-01T12:00:00Z",
  "status": "sent"
}

Dependencies

• Requires an API key credential for authenticating with the Tidio API.
• Needs configuration of Tidio API credentials including client ID, client secret, API key, and base URL.
• Uses an external proxy service (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.
• The file to be sent must be accessible via a public URL.

Troubleshooting

• Invalid Conversation ID: If the conversation ID does not exist or is incorrect, the API will return an error. Verify the conversation ID before sending.
• File URL inaccessible: The file URL must be publicly accessible. Private or expired URLs will cause the message to fail.
• Authentication errors: Ensure that all required API credentials are correctly configured and valid.
• API rate limits: Excessive requests may lead to throttling. Implement retries or delays if needed.
• Malformed additional fields: Custom properties must be valid JSON; invalid JSON will cause errors.
• Send As Bot flag: If set incorrectly, messages might appear from the wrong sender identity.

Common error messages:

• "Unknown resource" or "Unknown message operation" indicate misconfiguration of resource or operation parameters.
• Network or timeout errors suggest connectivity issues with the Tidio API or proxy service.

Links and References

• Tidio API Documentation
• n8n Documentation on Creating Custom Nodes
• Tidio Live Chat Official Site