Coming from Mavibot?
Mavibot combines chatbot message chains with an AI assistant, integrations and Telegram commerce features. Whenever is another way to build a custom cross-tool bot: describe the rules and allowed actions, then review sample outcomes and run history. Model replies can vary and consume runtime AI; free AI building has weekly usage 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.
Messages per day. Runs per month.
Mavibot daily usage includes blocks and some API requests, not only chat messages, within a project subscription. Whenever counts workflow executions and runtime AI separately.
Mavibot
Monthly plans with daily message limits
Daily usage per project, including blocks and API requests
A free plan has a daily message cap. Extra messages, messengers and employee accounts are paid add-ons for Business and MaviBot AI plans.
Mavibot subscriptions apply per project. Its message statistics include sent blocks, empty messages, external-service requests and incoming API requests; these are not simply customer chat messages. Its AI assistant and chatbot builder work together. Compare the applicable plan and actual usage with Whenever runs and runtime AI, not message counts alone.
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
Mavibot
Message chains follow configured rules, and the integrated AI assistant can generate replies and use configured tools. Separate fixed rules from model decisions when testing repeatability.
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
Mavibot
Plans have daily usage allowances per project. Paid add-ons for messages, messengers and employee accounts apply to Business and MaviBot AI, not every plan.
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
Mavibot
A builder of message chains and funnels, plus API requests from inside the bot, Google Sheets and payment processors.
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
Mavibot
Mavibot documents downloading a bot flow as JSON and restoring it in Mavibot. This is a real export; importing that flow into a different runtime is a separate migration question.
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
Mavibot
Mavibot documents CRM analytics widgets for deals and clients, filterable by funnel block, channel and list.
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
Mavibot
Mavibot documents an AI plan and an AI assistant integrated with the chatbot builder. Check the model and plan usage for the configured assistant rather than assuming chains exclude AI.
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.
Where the bot talks
Mavibot
Telegram, WhatsApp Business API, Instagram, Discord, TikTok, Viber and LINE are connected per project.
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
Mavibot
Mavibot documents Python programming and builder/editor APIs. This comparison did not test authoring its bots 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 Mavibot
Mavibot
Keep it for selling inside Telegram: in-chat payments, a mini-app shop, broadcasts to your subscribers, bookings, paid clubs, and a multi-step form that remembers each answer.
Whenever
Use Whenever for a bot whose rules you want as a workflow file that calls the integrations you authorise. It does not keep conversation memory between messages for you.
Sources and scope
Captured official documentation distinguishes per-project subscriptions and message statistics from customer messages. Conflicting student allowances are not quoted. No current competitor dollar price is asserted.
Checked
Telegram 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 workflowAsk a Telegram bot for your agenda and inboxReplies to /today with your calendar and open tasks and to /inbox with a one-line summary of each unread email. After publishing, you pick a secret token in Whenever and pass it with the webhook address to Telegram's setWebhook; one bot serves one workflow.
Build this workflowSchedule Telegram channel posts from a sheetPublishes due rows from your posting sheet to Telegram on the cadence you choose, then marks each row Posted.
Build this workflowGet Telegram alerts on big price movesChecks your tickers every hour and messages you on Telegram when one moves more than your threshold within that hour.
Build this workflowCollect leads in a Telegram bot conversationAsks for name, email, phone and company one question at a time, keeps the answers in a sheet, and adds each finished lead to HubSpot. After publishing, you pick a secret token in Whenever and pass it with the webhook address to Telegram's setWebhook; one bot serves one workflow.
Build this workflowSend yourself a morning digest on TelegramDelivers one Telegram message each morning with your unread email, today's meetings and the tasks due.Build this workflowStart with one Telegram command.
Describe what it should answer and which tools it may use. Whenever writes it as code you keep.
Pick a question you answer by hand
“What’s on today”, “where’s my order”, “what came in overnight”: questions your other tools can answer.
Describe it and connect your bot
Say what the bot should do and which apps it may use. Whenever writes it; review the rules, then connect your BotFather token.
Publish, then register the webhook
Test it with real messages, publish it, and point your Telegram bot at its webhook address once.