N8N Tools - Tidio API icon

N8N Tools - Tidio API

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

Actions31

Message → Send Typing Indicator

AI-generated

Overview

This node integrates with the Tidio API to manage live chat conversations and messaging. Specifically, the Send Typing Indicator operation under the Message resource allows you to show a typing indicator in an ongoing conversation. This feature is useful for enhancing user experience by signaling that an operator or bot is actively preparing a response.

Practical scenarios include:

  • Indicating to a visitor that a customer support agent is typing a reply.
  • Showing chatbot activity during automated interactions.
  • Improving engagement by providing real-time feedback in chat sessions.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation where the typing indicator will be sent.
Additional Fields A collection of optional fields (not used directly in this operation but available generally).

The Additional Fields collection includes various optional parameters such as visitor/contact details, tags, custom properties, status, priority, etc., but these are not applicable for the Send Typing Indicator operation itself.

Output

The output JSON contains the raw response from the Tidio API after sending the typing indicator. It typically confirms the success of the request or provides error information if the operation failed.

No binary data is produced by this operation.

Example output structure:

{
  "json": {
    // API response confirming typing indicator was sent
  }
}

Dependencies

  • Requires an API key credential for authenticating with the Tidio API.
  • Needs configuration of the Tidio API URL and client credentials (Client ID and Client Secret).
  • The node uses an external proxy service (https://n8ntools.io/api/v1/proxy/tidio) to forward requests to the Tidio API.

Troubleshooting

  • Common issues:

    • Invalid or missing conversation ID will cause the API call to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems may prevent reaching the proxy or Tidio API.

  • Error messages:

    • Errors returned from the API are passed through in the output JSON under an error field.
    • If the node is set to continue on failure, it outputs the error message instead of stopping execution.
    • To resolve errors, verify the conversation ID, ensure valid API credentials, and check network access.

Links and References

Discussion