Chatwoot icon

Chatwoot

Interact with Chatwoot API

Overview

This node operation updates the status of a specific conversation within an account on the Chatwoot platform. It allows users to change the state of a conversation to one of several predefined statuses such as "Open", "Pending", "Resolved", or "Snoozed". This is useful for managing customer support workflows, where conversations need to be tracked and categorized by their current handling stage.

Practical examples:

  • Marking a newly received customer inquiry as "Open" to indicate it requires attention.
  • Changing a conversation status to "Pending" when waiting for customer response.
  • Setting the status to "Resolved" once the issue has been addressed.
  • Snoozing a conversation temporarily if follow-up is needed later.

This operation helps automate and streamline conversation management in customer support systems integrated with Chatwoot.

Properties

Name Meaning
Account ID The numeric ID of the Chatwoot account containing the conversation.
Conversation ID The numeric ID of the conversation whose status you want to update.
Status The new status to set for the conversation. Options: Open, Pending, Resolved, Snoozed.
Continue on Fail Whether to continue executing subsequent items if this operation fails (true/false).

Output

The output is a JSON object representing the updated conversation resource returned from the Chatwoot API after the status change. It contains all details of the conversation including its new status and other metadata.

No binary data is produced by this operation.

Example output structure (simplified):

{
  "json": {
    "id": 123,
    "status": "resolved",
    "contact_id": 456,
    "inbox_id": 789,
    "messages_count": 10,
    "assignee_id": 1011,
    "custom_attributes": { ... },
    ...
  }
}

Dependencies

  • Requires an active Chatwoot account and API access.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL of the Chatwoot instance must be set in the credential configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID or Conversation ID will cause request failures.
    • Insufficient permissions or invalid API token may result in authorization errors.
    • Providing an unsupported status value will cause the API to reject the request.
  • Error messages:

    • "404 Not Found": The specified conversation or account does not exist. Verify IDs.
    • "401 Unauthorized": Authentication failed. Check API token and credential setup.
    • "400 Bad Request": Invalid input parameters, e.g., unsupported status value.
  • Resolution tips:

    • Double-check that Account ID and Conversation ID are correct and exist.
    • Ensure the API key credential is valid and has necessary permissions.
    • Use only allowed status values: open, pending, resolved, snoozed.

Links and References

Discussion