Google Calendar and Google Tasks
Tasks are read from Google Tasks and blocks are written to your calendar. Anything already in the calendar is treated as busy.
Roadmap
What Diarized does today, what is being built, and the part most of these pages leave out: what we looked at and decided against, with the reason. If your task app is in that last section, that is the honest answer rather than a silence.
Live
Working now, for everyone.
Outlook and Microsoft To Do
The same on a Microsoft account. Outlook meetings count as busy time even when the blocks themselves go to Google.
Todoist
Tasks, priorities and due dates. Duration is a paid Todoist feature, so on the free plan you write 45m in the title instead.
Notion
Any database, once you have said which of its columns mean duration, priority and done.
TickTick
Tasks from your lists. TickTick's API cannot see the Inbox, so anything sitting there is not visible to Diarized, and we tell you so rather than reporting a sync that found nothing.
ClickUp
The only one of these with a real duration field on its free plan: a ClickUp estimate is booked as exactly that, with nothing to write in the title. Work due in the next few days is scheduled; ClickUp has no sprint to mean “now”, and booking a whole backlog would fill every hour you have.
Jira
The issues assigned to you in an open sprint, with their time estimate or story points turned into hours. Jira Cloud only, and the priority mapping is approximate: schemes are per-project and Jira has five levels where the scheduler has four.
Asana
Tasks assigned to you are read and scheduled. Asana has no duration or priority field of its own. Both are custom fields your workspace created, so you point Diarized at yours once and it reads them from then on.
Linear
The issues assigned to you, in your active cycle. Estimates become minutes at a rate you set, because a point means an hour on one team and a week on another. If your team runs no cycles, everything assigned to you is scheduled instead.
Every block explains why it is there
Each scheduled block links to a page explaining why it is where it is: what it was competing with, and what it lost to.
Important work wins the better slot
An important task takes the better slot even when a shorter one would have filled the gap more neatly.
Export everything, or delete everything
Export everything as a file, or delete the account and everything attached to it, without asking anyone.
Live on Pro
Working now, on the paid plan.
Not todayPro
One click on a block pushes that task past today and lets the rest of the week absorb it. Before this the only honest options were to finish it or to leave it sitting there looking at you. Nothing is completed and nothing changes in the app the task came from. All that moves is the earliest day it may be booked.
This needs longerPro
Add half an hour to a task from its block, without opening the app it came from. Most of the time you only find out an estimate was wrong while you are sitting in the block being wrong about it. The new length is kept here, and forgotten the moment you change the estimate at source, so fixing it properly always wins over a correction made weeks ago from a calendar.
Not before a datePro
Some work cannot start until something else lands, and a due date means the opposite. A task can now carry the earliest day it may be booked, and is left alone until then rather than pulled forward into the first gap that fits.
Working on
Being built right now.
Paid plans
The free plan connects one task app and one calendar account, rebuilt once a day. Signing in with Google puts Outlook out of reach, and paying lifts that. The scheduling controls marked below are the other half of it: they are being built for the paid plan. Nothing that works today moves behind it. The free plan keeps everything it has, and the page explaining why each block landed where it did stays free for everyone. That one is the whole point of Diarized and is not for sale.
Microsoft verification
The same for Microsoft accounts. It requires a registered company, which is the part still in progress.
Planned
Chosen, in this order, not started.
Tasks that already have a start time stay at that timePaid plan when it ships
If a task carries a real start time (not a due date, an actual "this happens at 09:00"), it should be booked at 09:00 rather than dropped into the next free slot. Today that time is ignored and the task is placed wherever it fits, which is surprising in the one case where you had already made the decision. The care is in telling a start time apart from a deadline: most task apps use one field for both, and reading a 5pm deadline as a 5pm appointment would book your evening for you.
When something has a fixed time, it may want to be an event →
A gap between one block and the nextPaid plan when it ships
Right now one block can end at 11:00 and the next start at 11:00, which reads fine in a calendar and is not how a day works. You will be able to say how much room to leave (five minutes to write the notes up, half an hour to get across town ) and have it apply to everything booked after it.
Long tasks over more than one sittingPaid plan when it ships
A four-hour task needs a four-hour gap today, so on a busy week it is not booked at all. It should become three sittings across three days, with a shortest useful length so nothing lands as a pointless ten minutes. The care is in telling your second sitting apart from an accidental copy: get that wrong and we delete a block you wanted, so this one is being done slowly.
Different working hours for different kinds of workPaid plan when it ships
One set of working hours covers every task, so writing and expenses compete for the same morning. You will be able to keep deep work before lunch and let admin fall anywhere, without moving either by hand.
Spread work across the week, or get it done as early as possiblePaid plan when it ships
Blocks are packed into the earliest slots that fit, which finishes the week early and makes Monday look brutal. The alternative is to spread the same work evenly across the days you have. Both are right for different people, so it becomes a setting rather than a change.
Microsoft Planner
The next one to build, because it is the cheapest by a distance. Planner is part of Microsoft 365, so the sign-in and the plumbing are the ones Outlook and To Do already use. Planner keeps due dates and buckets but has no duration field of its own, so length will come from a label the way it does in To Do. Most people meet Planner as the Tasks tab in Teams without ever hearing the name.
GitHub
The issues assigned to you, in the same shape as Linear and Jira. GitHub has no estimate field at all, so duration would come from a label (the convention Todoist users already use) and priority from labels too, since GitHub has no notion of it.
Monday.com
Still chosen, and honestly further off than this list used to suggest. Two things hold it up. Monday is part-way through replacing how apps sign in, and the old way is expected to stop working this autumn, so there is no point building against it twice. The bigger one is that a Monday plan below Pro allows a thousand API requests a day across everything you have connected, not per app, and Monday has no way to ask for just your tasks, so reading them means checking every board. Done carelessly we would spend your daily allowance by lunchtime and break your other integrations doing it. We would rather be late than be that.
Looked at, not planned
Ruled out, with the reason.
Slack, Teams, Gmail and Outlook mail
A message becomes a task only if there is somewhere to keep it, and Diarized deliberately keeps no task list of its own. Diarized keeps no tasks of its own. Yours stay in Todoist or Linear or wherever they already live, and all we produce is calendar blocks. A starred email has no home in that, and building one would mean becoming a task manager, which is the one thing this deliberately is not. Send it to your task app and we will schedule it from there. Every one of the nine has an email or a share sheet for exactly this.
OneNote
The checkboxes really are readable: Microsoft Graph returns them as to-do tags in the page's HTML. The problem is what a page cannot hold: no due date, no priority, no duration, so every block would be a guess. Worse, nothing can search a notebook by content, so finding your checkboxes means downloading every page every time we sync. And the daily-list habit this would be for (carrying yesterday's unfinished lines onto today's page) reads to us as the old task vanishing and a new one appearing, so a task you have been carrying for a week would get a fresh block, and lose its old one, every morning. If you keep your day in OneNote, flagging a line as an Outlook task puts it in Microsoft To Do, which we already read.
Superlist
There is no public way to read your tasks out of Superlist. It has been an open request on their own board since 2023.
Apple Reminders
Apple changed Reminders in iOS 13 to a format no outside server can read. Reaching it would mean shipping a Mac or iPhone app to sit alongside this one, which is a different product. The good news is that your own iPhone can do a rough version of this today, free, with Shortcuts.
Apple Calendar
Writing blocks into iCloud means handing us a password to store. There is no sign-in like Google's or Microsoft's. We looked hard at this and decided against it: it would be the only credential Diarized ever holds, for one calendar among several we already support properly. Blocks written to Google or Outlook still show up in the Apple Calendar app if you have those accounts on your Mac or phone.
iCloud calendars as busy time
This one is genuinely easy: iCloud can publish a calendar as a read-only link with no password at all, and reading it would stop us booking over your Apple meetings. It is here rather than in Planned because it was chosen against, not because it is hard. Ask for it if you want it and that decision can change.
Things 3
There is no way to read Things from a server. Everything Things offers other apps (its links, Shortcuts, AppleScript) runs on your own Mac, so it would need a companion app sitting on your machine while Diarized works in the background whether you are there or not.
Trello
Re-checked 11 August 2026 and the answer has not moved. Trello's API still signs in the old way: a key and a token that never expires, rather than the modern flow every other app here uses. Atlassian proposed replacing it in March 2025 and it has still not shipped. A token with no expiry, sitting in our database, is a worse thing to hold on your behalf than the integration is worth. Cards also carry no duration or priority for us to read. If OAuth 2 lands, this becomes an easy yes.
Any.do
Any.do has no public API. Every integration it offers runs through Zapier, Make or a similar middleman, and connecting means pasting an API key rather than signing in. Those integrations are also part of Any.do's own paid plans, so this would only work for people already paying them. We would rather not sell you something that needs a second subscription to work.
Salesforce, HubSpot, Zendesk and other CRMs
These have tasks, and we could read them. But a CRM task is chase Acme about the renewal, a five-minute follow-up attached to a deal, not a block of work to build a day around. Ask us if you disagree; the APIs are not the obstacle.
Something you need missing from all four lists? Tell us. The order above is not fixed.