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 provides server-side moderation operations for a chat platform, specifically enabling management of user flags and moderation status. The "Unflag User" operation removes a moderation flag from a specified user, effectively clearing any prior moderation concerns flagged against them. This is useful in scenarios where a user was mistakenly flagged or after a review determines the flag is no longer warranted.
Practical examples:
- Automatically unflagging users after manual review clears their flagged status.
- Removing flags from users who have resolved issues or disputes.
- Managing moderation workflows by programmatically controlling user flags.
Properties
| Name | Meaning |
|---|---|
| Target User ID | The unique identifier of the user to remove the flag from. This is the user receiving the moderation action. |
Output
The output JSON contains the response from the chat service's unflag user API call. It typically includes confirmation details about the unflagging action. The exact structure depends on the underlying API but generally confirms success or provides relevant metadata.
No binary data is output by this operation.
Example output JSON snippet:
{
"success": true,
"user_id": "targetUserId",
"message": "User unflagged successfully"
}
Dependencies
- Requires an API key credential with permissions to perform moderation actions on the chat platform.
- The node uses a server-side client SDK to interact with the chat service's moderation API.
- Proper configuration of the API credentials in n8n is necessary for authentication.
Troubleshooting
Common Issues:
- Invalid or missing Target User ID will cause the operation to fail.
- Insufficient permissions on the API key may result in authorization errors.
- Network or connectivity issues can prevent successful API calls.
Error Messages:
"Unsupported operation: moderation.unflagUser": Indicates the operation name or resource is incorrect or not implemented.- API errors related to invalid user IDs or permission denied will be returned from the chat service and surfaced by the node.
Resolutions:
- Verify that the Target User ID is correct and exists in the chat system.
- Ensure the API key used has moderation privileges.
- Check network connectivity and retry if transient errors occur.
Links and References
- Stream Chat Moderation API Documentation
- n8n Documentation on Credentials
- MongoDB Query Syntax (used in filters) (relevant for other moderation queries)