Chatwoot icon

Chatwoot

Interact with Chatwoot API
Join our community

Actions36

Overview

This node integrates with the Chatwoot API to manage contacts and other resources within a Chatwoot account. Specifically, the "Delete Contact" operation allows users to delete a contact by its numeric ID from their Chatwoot account.

Common scenarios for this node include:

  • Automating cleanup of outdated or invalid contacts.
  • Integrating Chatwoot contact management into broader workflows.
  • Removing contacts that no longer need to be tracked or messaged.

For example, you might use this node in a workflow that deletes contacts flagged as inactive in your CRM system, ensuring your Chatwoot contact list stays current.

Properties

Name Meaning
Contact ID The numeric ID of the contact to delete.
Continue on Fail Whether the node should continue processing subsequent items if deleting a contact fails.
Debug Logging Enables detailed logging of HTTP requests and internal operations to the console.

Output

The output JSON contains a single field indicating success:

{
  "success": true
}

This confirms that the contact was successfully deleted. If an error occurs, the node will throw an error unless "Continue on Fail" is enabled, in which case it outputs an error message object instead.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Chatwoot API.
  • The node uses the Chatwoot account ID and base URL from the provided credentials.
  • No additional external dependencies are required beyond access to the Chatwoot API.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID: Ensure the Contact ID is correct and exists in the Chatwoot account.
    • Authentication errors: Verify that the API key credential is valid and has appropriate permissions.
    • Network or connectivity problems: Check network access to the Chatwoot instance.

  • Error messages:

    • Errors from the HTTP request (e.g., 404 Not Found) indicate the contact may not exist.
    • JSON parsing errors do not apply here since no JSON input is parsed for deletion.
    • Enabling "Debug Logging" helps trace request URLs, headers, and responses for diagnosing issues.

  • To resolve errors, verify inputs, credentials, and network connectivity. Use debug logs for detailed insights.

Links and References

Discussion