Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Webhooks Actions
- Teams Actions
- Custom Filters Actions
- Reports Actions
Overview
This node operation retrieves the list of members belonging to a specific team within an account. It is useful in scenarios where you need to manage or display team compositions, such as showing team members in a dashboard, syncing team data with other systems, or performing audits on team membership.
For example, if you have a customer support platform organized by teams, this operation can fetch all agents assigned to a particular team to monitor workload distribution or update permissions.
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 output JSON contains an array of team member objects associated with the specified team. Each object typically includes details about a team member such as their user ID, name, email, role within the team, and possibly status information.
If the node supports binary data (not indicated here), it would be used for attachments or media related to team members, but this operation primarily returns structured JSON data representing team members.
Dependencies
- Requires an API key credential for authenticating requests to the ChatWoot API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the ChatWoot API being accessible and the provided account and team IDs being valid.
Troubleshooting
- Invalid Account or Team ID: If the provided account or team ID does not exist or the user lacks permission, the API may return an error or empty results. Verify that the IDs are correct and that the API key has sufficient access rights.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly set up in the node credentials.
- Network Issues: Connectivity problems to the ChatWoot API endpoint will result in request failures. Check network settings and API availability.
- Unexpected Response Format: If the API changes its response structure, the node might fail to parse the output correctly. Keep the node and API version in sync.
Links and References
- ChatWoot API Documentation - Official API docs for detailed information on endpoints and data structures.
- n8n Documentation - For general guidance on using n8n nodes and managing credentials.