Actions116
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ļø Sessions Actions
- š Profile Actions
- š¼ļø Screenshot Actions
- š¤ Chatting Actions
- š¢ Channels Actions
- š¢ Status Actions
- š„ Groups Actions
- Add Participants
- Demote To Admin
- Create Group
- Get Groups
- Join Info Group
- Join Group
- Refresh Groups
- Get Group
- Delete Group
- Leave Group
- Get Chat Picture
- Set Picture
- Delete Picture
- Set Description
- Set Subject
- Set Info Admin Only
- Get Info Admin Only
- Set Messages Admin Only
- Get Messages Admin Only
- Get Invite Code
- Revoke Invite Code
- Get Participants
- Remove Participants
- Promote To Admin
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
- š Auth Actions
Overview
This node operation lists channels based on a specified session and user role. It is useful for retrieving channel information where the user has a particular role, such as OWNER, ADMIN, or SUBSCRIBER. For example, it can be used to fetch all channels owned by a user or channels where the user is an admin.
Use Case Examples
- List all channels where the user is the OWNER for a given session.
- Retrieve channels where the user has an ADMIN role to manage channel settings.
Properties
| Name | Meaning |
|---|---|
| Session | The session name to identify the user session for which channels are listed. |
| Role | The role of the user in the channels to filter the list by (OWNER, ADMIN, SUBSCRIBER). |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
channels- List of channels matching the session and role criteria.
Dependencies
- Requires an API key or authentication token to access the channel listing API.
Troubleshooting
- If the session name is incorrect or expired, the node may return an authentication error or empty results. Verify the session value.
- Incorrect role values may result in no channels being returned. Ensure the role is one of OWNER, ADMIN, or SUBSCRIBER.
- Network issues or proxy misconfiguration can cause request failures. Check proxy settings and network connectivity.
- If SSL certificate validation fails and 'Ignore SSL Issues' is not enabled, the request will be aborted. Enable this option only if you trust the source.