FreshChat icon

FreshChat

Send messages using FreshChat API

Message → Send

AI-generated

Overview

This node integrates with the FreshChat API to send messages to conversations within the FreshChat platform. It is useful for automating communication workflows, such as sending notifications, alerts, or responses from agents or bots directly into customer conversations.

Common scenarios include:

  • Automatically sending follow-up messages after a support ticket update.
  • Bots sending proactive messages or reminders in ongoing chats.
  • Agents sending personalized messages triggered by external events.

For example, you could use this node to send a message from a bot to a specific conversation when a new order is placed, informing the customer about their order status.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation where the message will be sent.
Actor Type The type of sender: either an "Agent" (human support) or a "Bot" (automated system).
Actor ID The unique identifier of the agent or bot sending the message.
Message Type The visibility of the message: "Normal" (visible to all participants) or "Private".
Message The text content of the message to be sent.

Output

The node outputs JSON data representing the response from the FreshChat API after sending the message. This typically includes details about the created message object, such as its ID, timestamps, and status.

No binary data output is produced by this node.

Dependencies

  • Requires an active FreshChat account and API access.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for API requests is taken from the credential configuration.

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.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
  • Actor ID/Type Mismatch: Providing an actor ID that does not correspond to the specified actor type (agent or bot) may result in errors.
  • Message Content Issues: Sending empty or malformed message text can cause request failures. Always provide valid non-empty text.
  • API Rate Limits: Frequent message sends might hit rate limits imposed by FreshChat; handle such errors by implementing retries or delays.

Links and References

Discussion