Coming from MEE6?
MEE6 provides configured Discord plugins for moderation, levels, welcomes and alerts, with custom-bot branding subject to plan terms. Whenever offers custom Discord interaction or scheduled-API workflows you describe and supervise. Connected actions depend on each service’s API, permissions and plan. AI building has weekly limits; the workflow file is yours.
What you get on Whenever
Test each integration before you publish
Choose integrations from Whenever’s 1,400+ catalogue or provide a documented API. Availability and actions depend on the service’s API, permissions, plan and reachability from the hosted runtime; a catalogue listing is not a guarantee that every operation or sign-in method is supported. Test the specific lookup or update before publishing.
Map, summary, run history and code
Review the workflow map, summary and run history. Run and step logs are retained for 7 days on Hobby and 30 days on Pro. The code can be downloaded and handed to a developer; that is not a guarantee that a reported action succeeded in an external service.
What one Whenever plan covers
One plan can run bots and other workflows within its live-workflow, run and AI-spend limits. At a limit, contact Whenever about a larger plan; external services may bill separately. Hobby permits one active workflow.
A concrete decision
Illustrative scenarios, not customer results or recorded runs.
Greg: answer an order question safely
Illustrative decision, not a recorded customer run: Greg wants a team-chat bot to look up an order ID and report shipping status, without issuing refunds. He specifies the allowed lookup and tests found, missing and ambiguous orders with authorised accounts. He checks the returned provider status and run history, not a model’s unsupported “done” message or source code. A failed lookup should be reported as unconfirmed, not as a shipped order. Choose a custom procedure for that cross-tool rule; keep a specialised helpdesk if its ready-made experience fits. Model-written replies can vary and use runtime AI; this example is not proof of a delivered customer action.
Jaunius: choose the trigger before pricing it
Illustrative calculation, not observed traffic: a 15-minute schedule requires Pro and runs 96 times a day, or 2,880 times in a 30-day month, even when nothing arrives. A supported inbound trigger counts the executions it starts: for example, WhatsApp Business messages or Discord slash commands, buttons and modals. Scheduled workflows can also call channel APIs. Jaunius chooses the trigger and tests duplicate events and tool permissions. Compare the subscription, run and AI allowances and external charges; 2,880 checks are not automatically 2,880 messages or a saving.
A plan per server. A Whenever plan within its limits.
MEE6 sells Premium one Discord server at a time, with AI sold separately. Whenever meters runs across every workflow you have, bot or not.
MEE6
Premium per server
One subscription for each Discord server
The custom bot is an add-on to monthly Premium and included on yearly and lifetime. MEE6’s AI services are sold separately.
MEE6 sells Premium per Discord server and its AI services separately. Whenever subscriptions include workflow-run and runtime-AI allowances with plan limits. No current MEE6 price or regional price variation is asserted here.
A run is one execution of one workflow, start to finish. AI building and editing are free within weekly usage limits; runs are metered separately.
A closer look
What changes when you describe the job in plain language and code runs it: to build, to run, and to keep.
Repeatable execution logic
MEE6
Configured plugins and commands follow their settings; AI persona replies add model-generated content. As with other integrations, changing Discord data and permissions can change outcomes.
Whenever
The published code sets the bot’s allowed tools and execution limits. Review its rules and sample results; source-code inspection is optional. A model can choose wording and offered tools, so identical messages need not produce identical replies. Restrict permissions as well as the offered tools.
Runs per dollar
MEE6
Premium is bought per Discord server and unlocks Premium plugins. The custom bot is an add-on on monthly Premium and included on yearly and lifetime Premium; AI services are purchased separately.
Whenever
Pro includes 10,000 runs per month; see current US dollar subscription pricing. Each workflow execution counts once within its call budget. Scheduled API checks count even when idle; supported inbound events count when they start a workflow. Runtime model usage draws on the plan’s included AI spend in runs. If you reach a run or AI-spend limit, contact Whenever about a larger plan; no self-serve overage price is published. AI building has separate weekly limits.
What you can express
MEE6
MEE6 documents configurable plugins and custom commands for Discord server tasks, including moderation, levels and alerts. Check the plugin and plan needed for your job.
Whenever
Describe the bot’s allowed actions and handoff rules in plain language. Its tools can use 1,400+ integrations or a documented API, subject to permissions, provider-plan support and network reachability from Whenever’s hosted runtime. Review and test the results before publishing.
Export and portability
MEE6
Confirm which MEE6 configuration, data and credentials can be exported and what runtime is needed. This comparison does not treat an undocumented export as proof that none exists.
Whenever
The bot is a TypeScript file: its loop, its tools and its rules. Read it, export it, hand it to a developer. Moving it to another runtime can mean adapting managed connections and triggers.
Debugging a failed run
MEE6
MEE6 documents dashboard setup for its custom bot, with troubleshooting in its help centre and Support Server.
Whenever
Use the workflow map, summary and run history to inspect what happened, then ask for changes in chat and test representative messages. Run and step logs are retained for 7 days on Hobby and 30 days on Pro. Code is available when you or a developer want to inspect it.
Where the AI cost lands
MEE6
AI replies come from MEE6’s own AI services, bought separately from Premium.
Whenever
Optional model-written replies use the plan’s included AI spend in runs. At a run or AI-spend limit, contact Whenever about a larger plan; no self-serve overage price is published. Non-AI API operations do not require model inference, but external services may bill separately.
How fast it answers
MEE6
MEE6 documents slash commands and configured moderation and server features. These are feature claims, not a measured or guaranteed response time.
Whenever
Supported inbound events include Slack app events, Telegram bot updates, WhatsApp Business messages through a Meta app, and Discord slash commands, buttons and modal submissions. A scheduled workflow can also call the channel API; each scheduled run counts even when it finds nothing. This does not promise push delivery of ordinary Discord channel messages. Whenever does not host a website chat widget.
Building from your coding agent
MEE6
MEE6 documents dashboard setup for its custom bot. This comparison did not test building MEE6 features from a coding agent.
Whenever
Connect Claude Code, Cursor or Codex to the Whenever MCP server. Your coding agent can write and test the workflow and save it as a draft; complete Setup and publish after reviewing the result.
When to keep MEE6
MEE6
Consider keeping MEE6 for its configured moderation, levels and server plugins when they already meet your needs; measure response behavior on your own server.
Whenever
Use Whenever for a Discord job you want written as a workflow you can review and keep, using the integrations you authorise.
Sources and scope
Official sources captured on the date shown below. These describe published features and billing rules, not independent performance tests. Check the linked documentation for current modes, plans and limits. No competitor dollar price is asserted.
Checked
Discord bots to start from
Starter briefs for related jobs, not recorded runs. Connect authorised accounts, confirm trigger and plan requirements, then review and test the workflow before publishing.
Build this workflowDraw Discord giveaway winners at a set timePicks random winners from everyone who reacted to your giveaway post once the draw time passes, and announces them in the channel.Start with one Discord job.
Describe what the bot should do. Whenever writes it as code that uses the integrations you authorise.
Pick one Discord job to add
A welcome that also adds a CRM contact, a support request that becomes a thread and a row, a weekly recap of the server.
Describe it and connect the bot
Say what should happen in plain language. Whenever writes it and connects your Discord bot; review the summary and test its outputs before publishing.
Test it, then publish
Run it against a test channel first, then publish it on its schedule.