Discord server anti-impersonation / scammer tracker with data tables

Discord Member Change Tracker

This n8n template demonstrates how to automatically monitor and track username and nickname changes across your Discord server members. Perfect for community moderation, security monitoring, and maintaining accountability in large servers!

Use cases are many

Try tracking suspicious account behavior, maintaining audit logs for member identity changes, or monitoring impersonation attempts in your community!

Good to know

This workflow runs hourly by default - adjust the schedule trigger based on your server size and needs Discord API rate limits apply - large servers (1000+ members) may need longer intervals between checks Admin notifications are sent to a designated channel - ensure your bot has proper permissions The workflow maintains two separate databases: one for current member data and one for change history Protected usernames and admin roles can be configured to prevent false alerts

How it works

The Schedule Trigger initiates the workflow every hour to check for member changes Configuration Settings node stores your Discord server ID, admin channel ID, and protected user lists We'll fetch all server members using the Discord API, including their roles, nicknames, and user information The Edit Fields node extracts only the relevant data (user ID, username, nickname, roles) for processing Loop Over Items processes each member individually to compare against stored records If userID does not exist checks the main database - new members are added automatically The Switch node evaluates whether username or nickname has changed by comparing current data with stored records For first-time changes, a Discord message is sent to the admin channel and the change is logged in the tracking database If the user has changed their identity before, the workflow checks if this specific change is already recorded The aggregate all necessary data node compiles both old and new information for detailed comparison Multiple conditional branches determine exactly what changed (both fields, username only, nickname only, or neither) Database updates append new changes to existing records, creating a comma-separated history of all identity modifications Error handling catches edge cases where triggers fire but no actual changes occurred