Monitchat icon

Monitchat

Send messages to Monitchat

Actions7

Overview

This node integrates with the Monitchat platform to manage conversations and tickets. Specifically, the "Conversation Auto Reply" operation allows users to enable or disable automatic replies for a given conversation by updating its auto-reply status.

Common scenarios where this node is beneficial include:

  • Automatically managing customer support conversations by toggling auto-replies based on conversation context.
  • Enabling or disabling auto-replies programmatically as part of a workflow that handles incoming messages or ticket updates.
  • Integrating Monitchat's auto-reply feature into broader automation pipelines to improve response efficiency.

For example, a user could set up a workflow that disables auto-reply when a human agent takes over a conversation, ensuring customers receive personalized responses instead of automated ones.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation whose auto-reply setting you want to change.
Auto Reply Whether to send an auto reply or not. Possible values: true (enable), false (disable).

Output

The node outputs a JSON object representing the response from the Monitchat API after attempting to update the auto-reply status of the specified conversation. This typically includes confirmation of the updated state or error details if the request failed.

Example output structure (simplified):

{
  "success": true,
  "conversation_id": "123456",
  "auto_reply_active": true
}

If an error occurs and "Continue On Fail" is enabled, the output will contain an error message:

{
  "error": "Error message describing what went wrong"
}

The node does not output binary data.

Dependencies

  • Requires an API key credential for Monitchat to authenticate requests.
  • Makes HTTP requests to Monitchat's REST API endpoints.
  • Needs network access to https://api-v4.monitchat.com/api/v1.

No additional environment variables or external services are required beyond the Monitchat API key.

Troubleshooting

  • Common issues:

    • Invalid or missing API key: The node will fail to authenticate with Monitchat.
    • Incorrect conversation ID: The API may return an error if the conversation does not exist.
    • Network connectivity problems: Requests to Monitchat API may time out or fail.

  • Error messages:

    • "Não foi possível obter a lista de usuários ou o formato da resposta é inválido" (Portuguese for "Could not get the list of users or the response format is invalid") — indicates an issue fetching user-related data, possibly due to API changes or invalid credentials.
    • Generic HTTP errors returned by the Monitchat API will be passed through; check the error message for details.

  • Resolution tips:

    • Verify the API key is correct and has necessary permissions.
    • Confirm the conversation ID exists in Monitchat.
    • Ensure stable internet connection and that the Monitchat API endpoint is reachable.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.

Links and References

Note: The above links are inferred and should be verified for accuracy.

Discussion