Back to Guides Hub

Best practice setup

CleanerBot Bulk Upload Guide

Understand why CleanerBot does not auto-import your full member roster after installation, and how to seed known members quickly with /bulk_user_upload.

Invite CleanerBot Open command reference

Why CleanerBot does not auto-import every member

CleanerBot is built around a privacy-first model and does not rely on privileged intents for core operation. That means it does not automatically pull a complete member roster at install time.

Normal inactivity tracking still works without any bulk import. As members interact and admins use regular commands, CleanerBot learns and tracks them over time.

When bulk upload helps: large or structured communities that already maintain a known roster and want faster day-one coverage.

What /bulk_user_upload does

  • You can provide either comma-separated IDs (ids) or a CSV attachment (file).
  • CleanerBot checks those IDs against your current server.
  • Valid members are seeded for inactivity tracking faster.
  • Existing known members are skipped as already known.
  • The command keeps CleanerBot's privacy model intact and does not require message content access.

How to get user IDs

CleanerBot does not generate a full member ID export by itself. Use this command when you already have a member roster.

Some admins use third-party tools to export members and then copy IDs into CleanerBot. Two examples tested by our team:

MemberList

/server filetype:csv

ServerStats

/members filter:members only file:csv file

Third-party note: these tools are not operated by CleanerBot. We do not control their uptime, output format, permissions, or privacy practices.

Recommended upload workflow

  1. Export member IDs from your trusted roster source.
  2. Preferred path: upload the CSV directly via /bulk_user_upload file:<members.csv>.
  3. Alternative path: use ids with comma-separated IDs (up to 250 unique IDs per run).
  4. Watch progress updates and read the final summary.
  5. CSV mode handles full files in internal batches; manual ids mode may require repeated runs.

Understanding the result summary

added: members successfully registered for tracking.
known: members already known to CleanerBot.
not found: ID not found or user not in your server.
invalid: entry is not a valid user ID.
error: CleanerBot could not fetch that ID at this moment.

Limits and plan notes

  • /bulk_user_upload is available on Pro and Scale.
  • Manual ids mode keeps the existing 250 unique IDs per command limit.
  • CSV file mode does not apply the 250-ID per-command cap and processes full files in internal batches.
  • Bulk upload is optional. Normal inactivity tracking continues to work without it.

Next steps

If your current coverage is below target, run /coverage first, then seed with /bulk_user_upload (preferred: CSV upload).

Open /coverage docs Open /bulk_user_upload docs