job: inbox-triage · weekdays 07:30

Gmail AI assistant for inbox triage

Every weekday at 07:30 dassi works through your unread Gmail in the browser you're already signed into. Newsletters and receipts get labeled and archived, the replies you taught it get drafted, and you open a short list of what actually needs you. Nothing goes out unless you approved it or allowed that kind of reply.

Give dassi this job

Free credits, good for 7 days — no card required

Trusted by 30,000+ Chrome users Rated 4.8/5 on Chrome Web Store Works with Claude, GPT, Gemini, and more

One run, start to finish

Every dassi job has the same shape: an input, work done on real pages and accounts, output you can verify, and exceptions flagged — never guessed. This one is an illustrative example of the job.

run · inbox-triage scheduled · weekdays 07:30 illustrative example
input

“Triage everything unread since yesterday. Sort by my rules, archive newsletters and receipts, draft the usual replies, and give me the list of what needs me.”

Scheduled workflow: your Gmail, your labels, your rules in plain English

run
  1. 07:30 mail.google.com opened your inbox in your signed-in session and read the 47 messages unread since yesterday's run
  2. 07:36 mail.google.com sorted them by your rules: 8 customers, 6 vendors, 19 newsletters, 11 receipts, 3 that matched no rule
  3. 07:40 mail.google.com labeled and archived the 19 newsletters and 11 receipts
  4. 07:43 sheets.google.com logged the 11 receipts in your expenses sheet: vendor, amount, date, and a link back to each email
  5. 07:49 mail.google.com drafted 5 replies from patterns you taught (3 order-status answers, 2 meeting confirmations) and sent 2 invoice acknowledgments, the one reply type you let go out on its own
  6. 07:52 mail.google.com wrote your digest: the 10 threads still waiting on you, one line each on why
output
  • verified: 30 messages labeled and archived, and 11 receipts logged in your sheet with links
  • verified: 5 reply drafts held for your approval; 2 invoice acknowledgments sent under your standing rule
  • verified: A digest of 10 threads that need a person, each with a one-line reason
exceptions
  • flagged: A customer asked for a $340 refund, above the $200 you let dassi draft for. No draft written; it's first in the digest
  • flagged: A long-time vendor asked you to update their bank details from a domain that didn't match their past invoices. No reply, no archive, flagged in the digest as possible fraud
next

Tomorrow at 07:30, only mail that arrived since this run. Change a rule in plain English and that run uses it.

What you can hand off

Sorting by your rules

Customers, vendors, newsletters, receipts, or whatever buckets you actually keep. The rules are plain English and map onto the Gmail labels you already use.

Label and archive the obvious

Newsletters, notifications, and receipts leave the inbox with the right label on them, so search still finds them in March.

Replies drafted from your patterns

Order status, meeting confirmations, the invoice resent for the third time. Show it a few replies you've sent and it drafts new ones in the same shape, saved in Drafts.

Receipts into a sheet

Vendor, amount, and date pulled from receipt emails into your Google Sheet, each row linked to the message it came from.

The morning digest

A short list of the threads that need a human, one line each on why. Usually short enough to read before your first call.

Why does the inbox eat the first hour?

Most of what lands in Gmail overnight doesn’t need you, and the part that does is scattered through the rest, so the morning goes to opening forty-odd messages to find the ten that matter. Gmail’s tabs help a bit. They sort by what Google guesses a message is, which is a different question from the one you care about: is this a customer, is this the vendor who’s been hinting at a price increase since June, is this a receipt your accountant will ask about in April.

Filters are the usual fix. They hold up for about a month (filters are good at sender addresses and hopeless at intent), and then your biggest customer writes in from a personal Gmail account and lands in a folder nobody opens.

The 07:30 run

At 07:30 on weekdays dassi opens Gmail in the browser you already use, signed in as you, and reads what’s unread since yesterday. It sorts by the rules you wrote in plain English. Newsletters and receipts get labeled and archived. The receipts also become rows in your expenses sheet, each with a link back to the email, which sounds minor until the first time you need to find one in a hurry.

Replies you send constantly, like order status or “Thursday works,” get drafted in the shape of the examples you gave it and left in Drafts. Everything else goes into a digest with one line per thread on why it needs you.

A refund request above your limit goes to the top of the digest with no draft, since you set $200 as the most it drafts a refund reply for. A vendor you’ve paid for two years asking to change bank details, from a domain their invoices never came from, gets flagged and left alone. Could be fraud. Could be a vendor who switched banks and set up their email badly. dassi can’t tell which from the inbox and neither can you, so that one ends with you picking up the phone.

If you’re on Outlook, the setup is the same. dassi reads what’s on screen instead of calling an API, so folders and categories stand in for labels and your rules carry over.

Sending stays with you

Every reply is a draft until you approve it. You can let one narrow type go out on its own (invoice acknowledgments tend to be first, since nobody was ever harmed by “got it, thanks”), and each automatic send still shows up in the run record.

We’d keep that list short, for a reason that has little to do with dassi. Email is text from strangers, and some of it is already being written to talk AI assistants into things. The worst thing a draft can do is sit there until you delete it.

Limits

The browser has to be open when the run is due, because that’s where it runs. Laptop asleep in a bag at 07:30 means no triage that morning.

To sort a message the model has to read it, so the content of each email dassi processes goes to the AI provider you picked: under your own key if you brought one, or through dassi’s relay if you’re on included credits. Senders or labels you’d rather keep away from any model can be excluded by a rule, and they’ll sit in the inbox untouched.

Then sign-in. If Gmail has logged you out, dassi uses whatever your browser’s password manager autofills, and Google’s 2-step prompt comes to you. The password stays in the password manager and never goes into a chat or into dassi’s settings.

Setting it up

Write the rules, point it at a handful of replies you’ve sent for each pattern, and read the first digest slowly. Expect to rewrite a rule or two after that. We still haven’t seen a clean rule for the newsletter you archive every week and then go hunting for on Friday afternoon, so maybe that one stays manual.

Teach it once

01

Write your rules down once

Who counts as a customer, which senders are newsletters, what a receipt looks like. Plain English, editable whenever your inbox changes.

02

Show it the replies you repeat

Point it at three or four replies you've already sent for each pattern. New drafts come back in that shape and tone.

03

Pick what may send on its own

Every reply waits for you by default. If one reply type is dull enough, like an invoice acknowledgment, you can let that type go out without review.

Your accounts. Your machine. Your call.

Runs on your machine

The agent works in your browser on your computer, local by design. It never runs in our cloud.

Your logins stay yours

It works in the sessions you're already signed into. No password handoff, no credential vault.

You approve what leaves

Messages, submissions, payments — anything outbound waits for the approvals you set.

Your model, your choice

Claude, GPT or Gemini with your own key or included credits, or a fully local model. On your own key, prompts go straight to your provider; included credits pass through dassi's relay.

Frequently asked questions

Does it work with Outlook too?

Yes. dassi reads the page in your browser rather than connecting through an API, so the Outlook web app works the same way Gmail does. Folders and categories stand in for labels, and your rules carry over.

Will it send email without asking me?

Only the reply types you've explicitly allowed. Everything else is saved as a draft and waits for your approval, and every send that did happen shows up in the run record.

Who can read my email?

dassi runs in your browser on your machine, but the model has to read a message to sort it. The content of each email it processes goes to the AI provider you picked: under your account if you use your own key, or through dassi's relay if you use the included credits. Senders or labels you never want sent to a model can be excluded with a rule.

What if someone emails instructions aimed at the AI?

It's a real risk. Email is text from strangers, and some of it will be written to steer an AI. That's why replies are drafts by default and why we'd keep the list of auto-send reply types short. Your rules can also tell dassi not to open links or attachments during triage.

Does my computer need to be on at 07:30?

Yes. Scheduled runs happen in your own browser, so it has to be open when the run is due. If you're rarely at your desk that early, schedule it later or start the run by hand when you sit down.

What happens if Gmail has signed me out?

dassi signs in with whatever your browser's password manager autofills. Your password stays in the password manager; you never paste it into a chat or into dassi's settings. If Google asks for a 2-step verification code, you complete that part yourself.

Give dassi its first run

Install dassi, open the pages this job lives in, and show it the work once. It runs from then on — your way, on your machine.

Add dassi to your browser

Free credits, good for 7 days — no card required

More jobs dassi runs

Sign up — get 10% off

Create your dassi account. We'll email your discount code + the desktop install link.

or