Actions60
- User Actions
- Channel Actions
- Accept Invite
- Add Members
- Add Moderators
- Archive
- Ban User
- Create
- Delete
- Delete File
- Delete Image
- Demote Moderators
- Disable Slow Mode
- Enable Slow Mode
- Get Config
- Hide
- Invite Members
- Mark Read
- Mark Unread
- Mute
- Mute Status
- Pin
- Query Channels
- Query Members
- Reject Invite
- Remove Members
- Send Action
- Send File
- Send Image
- Show
- Stop Watching
- Truncate
- Unarchive
- Unban User
- Unmute
- Unpin
- Update
- Watch
- Message Actions
- Moderation Actions
Overview
The node performs server-side operations on Stream Chat channels, specifically for the "Mark Read" operation in the Channel resource. This operation marks a specified channel as read, indicating that all messages up to the current point have been acknowledged by the user or system.
This is useful in chat applications where you want to programmatically update the read status of a channel, for example:
- Automatically marking a channel as read after processing incoming messages.
- Syncing read states between different devices or sessions.
- Clearing unread message indicators when a user views a channel.
Properties
| Name | Meaning |
|---|---|
| Channel Type | The type of the channel. Common options: "messaging" (1-on-1 chats), "team" (group channels), "livestream" (broadcast channels). |
| Channel ID | Unique identifier for the channel (e.g., "general", "random", "team-alpha"). Combined with type to form the full channel ID (CID). |
Output
The output JSON contains the response from the Stream Chat API after marking the channel as read. It typically includes updated channel state information reflecting the read status change.
No binary data is output by this operation.
Dependencies
- Requires an API key credential with permissions to perform server-side Stream Chat operations.
- The node uses the official Stream Chat server client library to interact with the Stream Chat API.
- Proper configuration of the API credentials in n8n is necessary for authentication.
Troubleshooting
Common issues:
- Invalid or missing Channel Type or Channel ID will cause the operation to fail.
- Insufficient API permissions can result in authorization errors.
- Network connectivity problems may prevent successful API calls.
Error messages:
"Unsupported operation: channel.markRead"— indicates the operation name or resource was not recognized; verify correct selection.- API errors related to invalid channel identifiers or permissions will be returned from the Stream Chat service and surfaced by the node.
Resolutions:
- Ensure Channel Type and Channel ID are correctly specified.
- Verify API credentials have the required permissions.
- Check network connectivity and retry if transient errors occur.