Actions113
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response Actions
Overview
This node interacts with the ChatWoot API to retrieve members of a specific team within an account. It is useful for scenarios where you need to list or manage users assigned to a team, such as displaying team members in a dashboard, auditing team composition, or automating workflows based on team membership.
For example, a customer support manager might use this node to fetch all agents in a particular support team to assign tickets dynamically or generate reports on team activity.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the team belongs. |
| Team Id | The numeric ID of the team whose members you want to retrieve. |
Output
The node outputs JSON data containing the list of team members associated with the specified team and account. Each member object typically includes details such as user ID, name, email, role, and other relevant metadata provided by the ChatWoot API.
If the API supports it, binary data output is not expected for this operation since it deals with user information retrieval.
Dependencies
- Requires an active connection to the ChatWoot API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for the ChatWoot instance must be set in the credentials configuration.
Troubleshooting
- Invalid Account or Team ID: If the provided IDs do not exist or are incorrect, the API may return errors or empty results. Verify that the IDs are correct and correspond to existing entities.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly configured.
- Network Issues: Connectivity problems can prevent the node from reaching the ChatWoot API. Check network settings and endpoint accessibility.
- API Rate Limits: Excessive requests may trigger rate limiting. Implement retry logic or reduce request frequency if needed.
Links and References
- ChatWoot API Documentation (for detailed API endpoints and response formats)
- n8n Documentation (for general guidance on using API nodes and credentials)