ChatWoot

Overview

The ChatWoot node for n8n allows you to interact with the ChatWoot API. Specifically, the Teams → List All Teams operation retrieves a list of all teams associated with a given ChatWoot account. This is useful for automating workflows that need to access or process team information from your ChatWoot instance, such as synchronizing team data with other systems, generating reports, or managing team-based automations.

Example use cases:

• Fetching all teams to display in a dashboard.
• Using team data to assign conversations or tickets automatically.
• Integrating ChatWoot team information with HR or project management tools.

Properties

• Account Id: Enter the numeric identifier for the ChatWoot account whose teams you want to list.

Output

The output will be a JSON array where each item represents a team. Each team object typically contains fields such as:

{
  "id": 123,
  "name": "Support Team",
  "description": "Handles customer support queries",
  // ...other team-specific fields
}

• id: Unique identifier for the team.
• name: Name of the team.
• description: (If available) Description of the team's purpose.

Note: The exact structure may vary depending on the ChatWoot API version and configuration.

Dependencies

• External Service: Requires access to a ChatWoot instance with API enabled.
• API Credentials: You must configure the chatwootApi credential in n8n, which should include:
  • Base URL of your ChatWoot instance (url)
  • API key or token with permissions to read teams
• n8n Configuration: Ensure the node is properly installed and credentials are set up in your n8n environment.

Troubleshooting

• Invalid Account Id: If you provide an incorrect or non-existent Account Id, the node may return an error or an empty result. Double-check the Account Id value.
• Authentication Errors: If the API credentials are missing or invalid, you may see errors like "401 Unauthorized" or "403 Forbidden". Make sure your API key/token is correct and has sufficient permissions.
• Connection Issues: Network problems or incorrect ChatWoot base URL can cause connection failures. Verify the URL and network connectivity.
• API Rate Limits: Excessive requests may trigger rate limiting by ChatWoot. Monitor your usage if you encounter "429 Too Many Requests" errors.

Links and References

• ChatWoot API Documentation
• n8n Documentation: Creating Credentials
• n8n Community Support