Claude just moved into your Notion workspace

Hey,

Notion's external agents just went live. Claude and Cursor can now be assigned work inside your workspace like teammates, not chatbots.

Email is still broken for most people's setups, and there's a fix for that too. And a self-described AI skeptic just got converted, with a caveat worth reading.

Let's get into it.

In Today's Email 👀

• Claude and Cursor can now be assigned work inside your Notion workspace like teammates

• Notion Mail is dead. Here are 3 ways to make email work in your setup

• Why you should never delete a task or note (and the one filter that fixes it)

• An AI skeptic got converted. Here's what changed their mind and what still breaks

3 Tips / Updates

1/ EXTERNAL AGENTS HAVE LANDED

Notion just opened the door for Claude and Cursor to work directly inside your workspace, not as a sidebar chatbot, but as actual collaborators you can @-mention like teammates. Assign them from a shared board and watch progress unfold on the page, visible to your whole team.

Think of it as Notion finally letting other companies build the suit instead of always building it themselves. Claude agents handle data analysis, coding, spreadsheet and slide generation, and document drafting, returning finished work straight to Notion. Cursor leans into engineering specifically, picking up bug fixes or feature requests and opening pull requests once it's done. Permissions stay tight either way. Claude agents only see what you explicitly share with them, nothing more.

One detail worth knowing before you connect anything: Claude usage runs through Notion credits rather than your own Anthropic account. Cursor skips that entirely and bills to your existing Cursor plan instead. → If your team already leans on Cursor for code, that's reason enough to start there.

2/ EMAIL IN NOTION: 3 WAYS THAT ACTUALLY WORK

Notion killed Notion Mail. Emails didn't stop mattering. Here are 3 ways to make them work in your setup right now.

Skills: teach it once, run it whenever. A skill is a briefing. Write it once, goal, inbox to check, Notion database to write to, schema, steps, and your personal AI follows it on demand. Say "execute log new CRM leads" and it pulls the sender details and logs them, no manual entry required. The 4 types worth building: summarizing (today's inbox digest), organizing (label by action required, read later, promotions), capturing (leads, invoices, tasks into the right database), and responding (draft replies from your knowledge base). Most of the time you don't need the email in Notion. You need the information from it in the right place. Skills cover 80% of that.

Agents: same flows, zero attention required. Skills are reactive, you trigger them. Agents run whether you're watching or not. Your personal AI (bottom right corner) is included in your seat. Custom agents are pay-per-call, roughly 30 credits a month for simple triage on a small model. Always test a skill manually first, then automate it. Keep skills as separate pages and have agents reference them rather than repeat them. One skill, multiple agents, updates in one place.

Workers + Gmail script: the actual email object in Notion. If you need the full email, sender, body, thread, sitting in a database row, that's now possible without a paid connector. The stack: a Google Apps Script fires a webhook when a labeled email arrives, a Notion Worker catches it, extracts the fields, writes one row per thread. The setup takes about 45 minutes if you let Claude build it. You'll need a Notion integration token from the developer portal saved to a .env file (never paste secrets in AI chat), the integration connected to your target page, and the Apps Script Claude generates pasted in. The grooming session, having Claude ask every clarifying question before writing a line of code, is the step people skip. Don't. "One row per thread or one per message?" matters. Answer it upfront.

9 out of 10 times you don't need the email object in Notion. You need what the email means for your system. Skills and agents handle that without any sync infrastructure. Workers is for the 1 case where you genuinely need it.

That's about 15% shorter and reads a bit snappier without losing any of the substance. Let me know if you want it cut further or if the ending feels too abrupt now without a wrap-up line.

3/ STOP DELETING, START ARCHIVING

Completed tasks and old notes feel like clutter in the moment, but they're often exactly what you need six months later when a client asks "didn't we already decide this?" Deleting throws that history away for good. Filtering it out of view doesn't.

The setup is a single filter. Build a checkbox property for "complete," then create two views off the same database: one filtered where complete is unchecked, one filtered where it's checked. Your daily view stays clean, but nothing is actually gone, and completed tasks still surface wherever else they're connected, a project page, a time tracking log, a broader area page, so you can trace back what got done and when.

For anything that doesn't belong in a database at all, old images, half-finished pages, random blocks you're not ready to delete, skip organizing it entirely. Create one catch-all page, favorite it for quick access, then just select whatever you want gone and drag it in. A messy bin beats a permanently deleted file every time.

Poll / From The Community

A self-described AI skeptic finally tried Notion AI and walked away converted. The sticking point for them was always the same: building a system in Notion meant doing the boring, error-prone setup work yourself, and if something broke, you were back in there manually fixing filters and views. Notion AI took that grunt work off their plate, and they admitted it changed their mind entirely.

There's a sharper point buried in there too. The reason AI ends up doing this kind of work isn't that AI is inherently the best tool for it. It's that Notion still doesn't have a UI for editing multiple views across linked databases at once. AI becomes the workaround for a UI gap, not a UX upgrade in its own right.

The replies split into two camps. One side backed up the database and formula use case specifically, saying AI shortens that work dramatically. The other side pushed back hard, pointing out it still struggles with PDFs inside pages and sometimes truncates meeting transcripts before it's done reading them. The most useful comment in the thread was the reminder that most "Notion AI is useless" takes come from people using it for the wrong jobs, not from the tool being broken.

Quick Links & Tools

Voice notes → Notion in 90 seconds (Thomas Frank)

Record a voice memo while walking, upload it to Google Drive or Dropbox, and get a full transcript, summary, and action items in Notion automatically. Free via Groq + Pipedream. The r/notion community keeps rediscovering this one, it consistently tops "how do you capture ideas on the go?" threads. If your capture system is a voice notes graveyard, this is the fix.

Apple Health → Claude → Notion (automatic, daily)

Set up Notion databases for your health metrics, give Claude the page links in a project, then say "update my stats" from your phone each morning. Claude queries Apple Health directly and populates the databases automatically. No manual entry. Works with Apple Watch, smart scales, anything that feeds into Apple Health.

Is Notion AI Worth It in 2026? (Criticnest)

Honest breakdown of the credit system, plan tiers, and real monthly costs. Useful reference before your next renewal conversation.