Actions6
- Friend Actions
- Group Actions
- Message Actions
Overview
This node integrates with the OneBot API to perform various operations related to bots, friends, groups, messages, and miscellaneous information. Specifically, for the Group resource and the Get Group Info operation, it retrieves detailed information about a specified group by its name or ID.
Common scenarios where this node is beneficial include:
- Fetching metadata about a group such as its name, ID, owner, member count, or other attributes exposed by the OneBot API.
- Automating workflows that require group details for decision-making or reporting.
- Integrating group information retrieval into chatbots or monitoring systems.
For example, you might use this node to get the current status of a group before sending announcements or to log group details periodically.
Properties
| Name | Meaning |
|---|---|
| Group Name or ID | Select a group from a dynamically loaded list or specify a group ID using an expression. This identifies the target group for which information will be retrieved. |
Output
The node outputs JSON data containing the group information returned by the OneBot API's "get_group_info" endpoint. The exact structure depends on the API response but typically includes fields such as group ID, group name, owner ID, member count, and other group-related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a OneBot API instance.
- Needs an API authentication credential configured in n8n (referred to generically as an API key or token).
- Uses internal helper functions to load options dynamically (e.g., group list) and to make HTTP requests to the OneBot API.
Troubleshooting
- Empty or invalid group ID: If the group ID is not provided or incorrect, the API call may fail or return no data. Ensure the group is selected correctly or the expression resolves to a valid ID.
- API request failures: Network issues or invalid credentials can cause errors. Verify the API endpoint is reachable and the authentication token is valid.
- Permission errors: The authenticated bot account must have permission to access group info; otherwise, the API may reject the request.
- Multiple items without forwarding mode: When processing multiple input items, if forwarding mode is off, each item triggers separate API calls. This can lead to rate limiting or performance issues.
Common error messages usually relate to HTTP errors from the API, such as 401 Unauthorized (invalid credentials), 404 Not Found (group does not exist), or 429 Too Many Requests (rate limiting). Resolving these involves checking credentials, group IDs, and API usage limits.