The situation
Two people, both paid in BTC:
- Person 1 has bills on fixed dates. They want cash every Monday, whatever happened during the week.
- Person 2 gets irregular payments, like a client invoice here or a payout there. They want each payment converted when it arrives, not days later on a fixed day.
Same goal, different triggers. Coinomatic offers one mode for each.
The problem and the decisions
The first step of the wizard asks: "How should this automation run?"
- Scheduled: "Convert on a daily, weekly, or monthly schedule, with optional scheduled withdrawals."
- 24/7 Monitoring: "Monitor for newly detected funds and convert automatically using event-based rules."
Questions that usually settle it:
- What drives your cash need? A date (rent, payroll, a hosting invoice) points to Scheduled. An incoming payment you want to act on points to Monitoring.
- Do you hold other BTC on the same account? With a calendar rule you decide how much of the balance is used. With Monitoring the focus is on new funds. In Monitoring you can set the amount to everything or a percentage.
- How predictable do you need the timing to be? Scheduled runs at a time you pick. Monitoring runs whenever a new deposit of your selected asset arrives.
Illustrative example
Illustrative example – made-up people and amounts, not a recommendation.
- Person 1 (Scheduled): fixed amount in BTC, every Monday at 9:00 a.m. ET, withdraw 100% of the USD right after conversion, no end date. Cash arrives on a rhythm. Some weeks the BTC price is higher, some weeks lower, so the dollar amount varies.
- Person 2 (Monitoring): each new client payment that arrives on Kraken is converted, and the USD is withdrawn. Older BTC already on the account before the automation was saved is not touched by the monitoring rule, because according to the app, deposits from before save are not replayed.
How each mode behaves when something is missing
This difference matters and isn't obvious:
- Monitoring: according to the Knowledge Base (Oct 9, 2026), a monitoring automation "can be saved paused when a required withdrawal destination has not been resolved." It waits until you fix the destination.
- Scheduled: in our live test (Oct 10, 2026), a scheduled automation with an unresolved destination was saved and ran as normal. The conversion completed, and the withdrawal was skipped and logged. Nothing paused.
So with Scheduled, a missing withdrawal method won't stop the conversions. It only stops the withdrawals, quietly. Check Connection before you save, whichever mode you choose.
How Coinomatic helps you set it up
- Step 1 (Mode): pick Scheduled or 24/7 Monitoring.
- Conversion, Timing, Withdrawal, End condition, Review: for Scheduled we've confirmed these steps and fields in our test. The Monitoring wizard has no Timing step, because it reacts to deposits instead of a schedule. We haven't run a Monitoring automation ourselves.
- Automations list: both types appear together with their status and last run.
- Logs: each run or event is listed with a short explanation.
What it looks like
[IMAGE TO ADD: L01_wizard-1-mode.png - Live test screenshot, Oct 10, 2026, anonymized. Mode step with Scheduled and 24/7 Monitoring.]
Live test, Oct 10, 2026, anonymized.
[IMAGE TO ADD: D01_automations-list-demo.png - Demo data – illustrative. A list mixing scheduled and monitoring automations.]
Demo data – illustrative. Names, statuses, and row layout for Monitoring are made up. In particular, the "Paused" scheduled row does not reflect what we observed live, where a scheduled automation did not pause.
[IMAGE TO ADD: D03_logs-demo.png - Demo data – illustrative. Example log entries, including a monitoring event.]
Demo data – illustrative. The "Qualifying deposit detected" and "Automation paused" entries are invented for the demo.
Time check
Model example, your numbers will differ.
Take a freelancer with ~4 BTC invoices a month. Assume a manual cash-out takes ≈20 minutes (17 for exchange work + 3 to match it to the invoice), an automated run ≈3 minutes to check, a ≈10-minute monthly review, and 20 minutes of setup spread over 12 months.
4 × (20 − 3) − 10 − 1.7 ≈ 56 minutes a month, modeled.
That's modest, and the mode choice barely changes it. The real difference is when conversion happens: on your calendar, or close to when the payment lands. Neither is "better" for price, and Coinomatic doesn't try to time the market.
Limits and how to check the result
- Monitoring execution has not been verified by our own test, so treat descriptions of it as documented, not tested.
- Missed scheduled runs are not backfilled.
- Small amounts may be skipped below the exchange minimum (ORDER_SIZE_TOO_SMALL).
- Plan limits apply to the number of automations. See the Pricing section. The 30-day trial includes Scheduled automations only, not 24/7 Monitoring.
- After the first run or event, look in Logs for both the conversion and the withdrawal entry.
Next step
Read the Knowledge Base guides Scheduled automation mode and Monitoring automation mode. Not sure yet? Start with a one-run scheduled test (article 15) to confirm your connection and withdrawal method.
Coinomatic is software that triggers actions on your connected exchange account (today: Kraken) based on rules you set. It is not a financial advisor, broker, or money transmitter, and it does not take custody of your funds. Nothing in this article is financial, tax, or legal advice.