OpenRuna
Sign in
← Workflows

Keep discord clean

14 nodes · splitInBatches, schedule, wait, discord, filter

Engine
n8n
Nodes
14
Trigger
scheduled/triggered
Source file
1609_Wait_Schedule_Automation_Scheduled.json

Workflow flow

IntegrationsSplitInBatchesScheduleWaitDiscordFilter
100%
TRIGGER

Every day at 9pm

Schedule

Get all Discord channels

Discord

Cool down Discord API rate limits

Wait

Cool down Message deletion API rate limits

Wait

Get messages from Channel

Discord

Filter Messages older than 7 days

Filter

Loop Over Messages

SplitInBatches

Cool down Get messages API rate limits

Wait

Loop Over Channels

SplitInBatches

Delete Message

Discord

10 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Keep discord clean. 14 nodes across splitInBatches, schedule, wait, discord, filter, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Keep discord clean" chains 14 nodes to move data between splitInBatches, schedule, wait, discord, filter. 14 nodes · splitInBatches, schedule, wait, discord, filter Execution begins at the scheduled/triggered trigger and flows through the 14 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 14-node flow from scratch.
  • Benchmark it against your current splitInBatches integration to spot missing steps or redundant nodes.
  • Study how data moves from splitInBatches to schedule before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the splitInBatches stack.

Example output

Imported into n8n, "Keep discord clean" exposes 14 configured nodes. Trigger type: scheduled/triggered. Integrations: splitInBatches, schedule, wait, discord, filter. Open each node after import to map credentials to your own splitInBatches and schedule accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Keep discord clean" JSON into a plain-English runbook, node by node. It can flag where splitInBatches rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for splitInBatches, schedule, wait, discord, filter. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Keep discord clean" — extract splitInBatches IDs and secrets into environment variables without changing the 14-node structure.

Frequently asked questions

How do I import "Keep discord clean" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Keep discord clean" use?
It uses: splitInBatches, schedule, wait, discord, filter. The flow diagram above shows how each service connects across the 14 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own splitInBatches and schedule credentials in n8n after import.
What trigger type does "Keep discord clean" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Keep discord clean" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for splitInBatches, schedule, wait, discord, filter.

Related resources