N8N Tools - Tidio API icon

N8N Tools - Tidio API

Complete Tidio integration - Live chat, AI chatbots, and customer engagement

Actions31

Conversation → Close Conversation

AI-generated

Overview

The node provides integration with the Tidio live chat and customer engagement platform, specifically enabling management of conversations. The Close Conversation operation allows users to programmatically close an active conversation in Tidio. This is useful for automating chat workflows where a conversation needs to be marked as finished or resolved after certain conditions are met, such as after sending a final message or completing a support task.

Practical examples include:

  • Automatically closing a chat session once a support ticket is resolved.
  • Closing conversations after a chatbot flow completes.
  • Ending inactive or timed-out chats to keep the conversation list clean.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation to close.
Additional Fields (Not used in this operation) No additional fields are required or supported for closing.

Output

The output JSON contains the response from the Tidio API after attempting to close the conversation. Typically, this will include confirmation that the conversation was closed or details about the updated conversation status.

Example output structure (simplified):

{
  "id": "string",
  "status": "closed",
  "updated_at": "timestamp",
  ...
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Tidio API.
  • Needs configuration of the Tidio API base URL and client credentials (Client ID and Client Secret).
  • The node sends requests through a proxy service hosted at https://n8ntools.io/api/v1/proxy/tidio using an API key for that proxy.

Troubleshooting

  • Error: Unknown conversation operation: closeConversation
    This indicates the operation name might be misspelled or not supported. Ensure the operation is set exactly to "closeConversation".

  • Authentication errors
    If the API key or client credentials are invalid or missing, the request will fail. Verify that the correct credentials are configured in n8n.

  • Invalid Conversation ID
    If the provided conversation ID does not exist or is malformed, the API will return an error. Double-check the conversation ID input.

  • Network or Proxy Errors
    Since the node uses a proxy endpoint, network issues or proxy downtime can cause failures. Check connectivity and proxy service status.

Links and References

Discussion