Actions38
- Message Actions
- Message Buzz Message Actions
- Message Batch Message Actions
- Message Image Actions
- Message File Actions
- Message Message Card Actions
- Message Message Reaction Actions
- Group Actions
- Group Group Member Actions
- Group Group Announcement Actions
Overview
This node interacts with the Lark Messenger API to obtain the speech scopes of members within a specified group chat. Speech scopes define what voice or audio-related permissions or capabilities each member has in the group. This functionality is useful for managing and auditing communication permissions in group chats, especially in scenarios where voice interactions are controlled or need monitoring.
Practical examples include:
- Retrieving which members in a group have permission to speak or use voice features.
- Auditing group member permissions before enabling voice-based meetings or announcements.
- Integrating with other workflows that adjust user permissions based on their speech scope status.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" (using an API token for tenant-level access) or "OAuth2" (using OAuth2 authentication). |
| Chat Id | The unique identifier of the group chat whose members' speech scopes you want to retrieve. |
| Options | Additional optional settings: - Use Custom Body: Whether to send a custom request body instead of the default one (boolean). |
Output
The node outputs JSON data containing details about the speech scopes of group members. This typically includes information such as member identifiers and their associated speech permissions or statuses within the group.
If binary data were involved (e.g., audio files), it would be summarized here, but this node focuses on JSON responses describing member speech scopes.
Dependencies
- Requires access to the Lark Suite Open APIs.
- Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- The base URL for API requests is
https://open.larksuite.com/open-apis. - Proper permissions must be granted to the API credentials to read group member speech scopes.
Troubleshooting
- Invalid or missing Chat Id: Ensure the Chat Id is correctly provided and corresponds to an existing group.
- Authentication errors: Verify that the selected authentication method is properly configured and the credentials are valid.
- Permission denied: The API credentials might lack necessary permissions to access group member speech scopes; check API scopes and roles.
- API rate limits: If many requests are made in a short time, the API may throttle calls; implement retry logic or reduce request frequency.
- Use Custom Body option: If enabled incorrectly, the request body might not match API expectations, causing errors; ensure the custom body format aligns with API documentation.