Actions113
- 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
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
- 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
Overview
This node operation retrieves detailed information about a specific team within an account. It is useful when you need to fetch the current configuration, members, or metadata of a particular team identified by its unique ID. Typical use cases include displaying team details in dashboards, synchronizing team data with other systems, or auditing team configurations.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account containing the team. |
| Team Id | The unique numeric ID of the team to retrieve details for. |
Output
The output JSON contains the detailed information of the specified team. This typically includes fields such as the team's name, description, members, creation date, and any other metadata provided by the API. The exact structure depends on the external service's response schema but generally represents a single team object.
No binary data output is expected from this operation.
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 uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Invalid Account Id or Team Id: If either ID is incorrect or does not exist, the API will likely return a "not found" error. Verify that both IDs are correct and correspond to existing entities.
- 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 can prevent the node from reaching the API endpoint. Check network settings and firewall rules.
- 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 schemas)
- n8n Documentation on Creating Custom Nodes