Navi can email you now
Shipped today: Navi can send results straight to your inbox — chat replies, scheduled cron output, and generated files as attachments. Chat is great when you're at the keyboard; email meets you the rest of the time.
Up until now, everything Navi did lived inside the chat. Ask a question, get an answer in the thread. Set up a cron job, results show up as a new chat message whenever they fire. That works beautifully when you're actively using Navi. It works less well when you're in meetings, on a plane, or just not looking at the app.
So Navi can now send email. Not from your Gmail — from Navi's own address, reports@send.naviwork.ai, straight to whatever email you signed up with.
How to use it
Just ask. Any chat turn that ends with "...and email me the result" will do it:
Navi does the work in the chat (you can watch), then fires off the email at the end. The message arrives in your inbox formatted as a real email — headings, bullet points, tables, links — not a wall of raw markdown.
There's also a button for it. Next to the paperclip icon in the chat composer, you'll find a little envelope. Click it and the phrase "Please email the result to me using email tool" gets appended to whatever you're typing. Handy for long-running tasks where you want to walk away while Navi works.
Where it really earns its keep: scheduled reports
Cron jobs are where this gets good. You already set up agents that run on a schedule — the 8am calendar briefing, the Friday Linear roll-up, the Monday planning sweep. Adding email delivery takes them from "post into a chat I might notice" to "land in my inbox at the time I need them."
The email shows up looking like a real product email — styled, readable on mobile, dark-mode aware. It's not a "notification" with a link back to the app; the content is the email.
Attachments
Navi can attach files too. Anything it produces or downloads in its sandbox — PDFs, spreadsheets, generated charts, scraped reports — can come along as an attachment.
Current limits: up to 10 files per email, 10 MB each, 25 MB total. If Navi tries to attach something bigger, it'll tell you in chat and ask how to trim it.
A few things worth knowing
The email goes to you, not to anyone else. This is a safety feature, not a limitation. The tool Navi uses is hard-wired to your own address — it literally cannot be pointed at someone else's inbox by accident or by a clever prompt. If you want to email a colleague, use the Gmail integration, which goes through your actual Gmail account with your from address.
Replies don't come back to Navi. If you hit "reply" on one of these emails, you're replying to a noreply-ish address that Navi doesn't read. Treat the emails as one-way delivery. To continue a conversation, go back to the chat — it's all still there.
The subject line is whatever Navi thinks fits. If you want to filter these in Gmail (say, to auto-label your daily briefings), tell Navi: "When you email these to me, start the subject with [Briefing] so I can filter." It'll remember.
The broader shape
Navi's design principle is: you describe the outcome, Navi figures out the steps. Email delivery is a small thing but it changes the texture of that outcome. You stop thinking about Navi as "an app I open" and start thinking about it as "the thing that puts finished work in front of me."
The 7:30am inbox arrival is the point. The chat is where the work happens; the inbox is where it lands.
Questions? Stuck? Want to share something you built?
Come join the Navi community — the fastest way to get help or compare notes with other users:
- Discord — real-time chat with the Navi team and other users
- r/naviwork on Reddit — longer-form tips, playbooks, and Q&A
- Navi Facebook group — for folks who prefer Facebook