Skip to content
Thendoo

Search

Planned

Gmail and Thendoo integration (planned)

Gmail is not connected to Thendoo yet. Here is what the planned integration is meant to do, why it comes later, and how to get email tasks into Thendoo today.

How often: Not syncing yet. This integration is planned.

What syncs

  • Planned: turning an email into a taskInto Thendoo
  • Planned: a triage view of your mailInto Thendoo
  • Planned: follow-ups on sent mail that got no replyInto Thendoo
  • Planned: labels and draftsFrom Thendoo

Set it up

  1. 1There is nothing to set up yet. Gmail does not appear in Settings, then Connections, because it has not been built.
  2. 2Meanwhile, when an email needs action, press Ctrl K (⌘K on a Mac) or choose Capture, and type the task the way you'd say it, such as "reply to Dana about the invoice tomorrow 10am". It takes a few seconds.
  3. 3If you are not ready to decide when, press Shift Enter to send it to the Inbox and sort it later with Sort one at a time.
Capture anything fast

Good to know

  • Gmail is not available in Thendoo today. Nothing reads, labels or sends your mail.
  • Reading Gmail needs what Google calls restricted scopes. For a hosted service, that means Google's app verification plus a yearly third-party security assessment before it can open to everyone.
  • The email-forwarding capture address is also planned, not built. Today, email tasks come in through Capture or the Inbox only.

Gmail is planned for Thendoo, not available. This page explains what the design calls for today, so you know what to expect and what to use in the meantime. Details can change before it ships.

What it is meant to do

When this ships, the plan is for Thendoo to work with Gmail in three ways.

  • Email to task. Turn a message into a task with a date, so it lands on Today instead of sitting in your inbox.
  • A triage view. A calm place to go through mail that needs a decision.
  • Follow-ups on sent mail. A nudge when something you sent got no reply.

The planned connection would read mail and work with labels and drafts.

Why Gmail comes later than the calendar

Google sorts permissions into tiers. Reading someone’s calendar is a sensitive scope. Reading their email is a restricted scope, the strictest tier. An app that stores or passes restricted data through its own servers has to pass Google’s verification and an independent security assessment every year.

Thendoo’s rule for every integration is to ask for the narrowest permission, and only the first time you use the feature that needs it. Email is the most private data most people have, so the design puts a simpler option first for the hosted service: a personal forwarding address you send emails to, which needs no access to your mailbox at all. Gmail itself is meant to follow once verification and the assessment are done.

How to handle email tasks today

You don’t need Gmail connected to stop emails from becoming a second to-do list. When you read something that needs action, capture one line with the next step and when you’ll do it. Capture understands dates, times, a Space with #, and an estimate with ~, so “reply to the landlord ~15m tomorrow #Personal” becomes a scheduled task. Then archive the email. Your inbox goes back to being mail, and Today holds the work.

Troubleshooting

I can't find Gmail in Connections.
That is expected: Gmail is planned and not built yet. Connections lists only Google Calendar and ClickUp today. Use Capture to turn an email into a task in a few seconds.
I connected Google Calendar. Can Thendoo see my email now?
No. The Google Calendar connection asks for read-only access to your calendars and events only. It does not include any Gmail permission.
Emails I need to act on keep getting lost.
Until Gmail is connected, capture the action, not the email. Write the next step and a date, such as "send Dana the signed contract Friday". Add the sender's name so search finds it later.

Checked against: developers.google.com/workspace/gmail/api/auth/scopes, developers.google.com/identity/protocols/oauth2/production-readiness/restricted-scope-verification