Introducing: the Notion Developer Platform New building blocks that help you (and your coding agents) sync any data source, build any tool, and orchestrate any agent. Follow along 👇 x.com/i/broadcasts/1AJEmOArr…

My agents are running My data is synced Enterprises thrive Notion in 5

Long story short: Claude Fable 5 is now in Notion. It's the model we'd put behind your most complex custom agents and workers. It set new highs on our internal benchmarks for the hardest multi-step work. Available on Biz and Ent plans.

Bonus: You can now read and write to your People directory DB via our API.

Meet Austin, Notion’s Workplace Experience Coordinator. He helps keep the SF office running smoothly and makes sure every new hire feels welcome. One painful part of his job has always been seat assignment: shuffling Notinos and Newtinos, one by one, going back and forth with managers, and starting over every two-week onboarding cycle. So Austin automated the entire seating shuffle end to end with custom agents and a Worker. It’s built using Notion’s developer platform, and connects OfficeSpace and Slack to Notion. Austin put it best: “It’s honestly super easy to set up a Notion worker… you’re just talking back and forth in plain English with Claude Code.” He split the job into two agents: Agent 1 watches the “New Hire” database. When a new name shows up, it posts to Slack and asks managers where to seat them. Agent 2 reads the replies and calls OfficeSpace to assign the seats. Now, instead of spinning up a new Slack channel every cycle and handling requests one at a time, Austin sends one message in Slack, and the agents do the rest. Austin: “I’m no engineer… but this saves me hours every time we onboard. It definitely made my life a lot better.” The best agents aren’t fancy, they just give you time back.

The amount of people RT-ing this because they want a story around model quality to be the reason is astonishing. The degraded performance was a temporary service disruption. This happens. It happens to Notion, GitHub, AWS, your OpenClaw, and everything in between. Ideally we don’t have to make you aware of this. That’s what Auto is for. We would ideally also not have to name upstream service providers. It’s bad form. Everyone can have a bad day. Unfortunately with model serving this can’t always be avoided. The real unlock: Anthropic model availability is restored. Have a great Sunday. 🤖 🚀

Look who stopped by HQ! @youtubejocoding

How do you build a brain? Everyone's talking about world models and unified enterprise data that agents and people can reason against but I haven't seen one live. So we built it at @NotionHQ, on Notion! We built a lot of AI agents on the People Team but quickly hit a wall. An agent is only as capable as the data it can reach and without people data, HR agents can't do much. But anyone in this space knows how difficult it is to make people data AI-ready. There's a reason why Workday isn't in Claude today. We've been thinking about this problem space for a while and here's how we're experimenting. Here's an onboarding demo. While seemingly simple, an onboarding agent in Notion is actually pulling from a single source of (governed & permissioned) data to personalize each new hires experience and sending the manager automated updates in Slack. We're using Human Intelligence's MCP here, pulling dummy data from Workday Ashby. It's super cool bc unlocking people data means having a truly unified data model. We can pull business data. Work context. All this will power the company of the future, and I'm excited we get to push the boundaries 😊

"The projects that I have the most fulfillment out of come from an aspect of fun... these ones that are inspired by art or different pieces of media...it's a different feeling when you can build it out and it feels like a little whimsical and magical in a way" full breakdown of his project ⬇️

Sync any data was not a lie 😎

We're finally shedding the .so (thank you Somalia!), and using the .com for @NotionHQ. And for this beautiful moment, I want to share a fun story: Back in 2018, I had just joined Notion, and one of the first things @ivan asked me to do was figure out how we could own notion.com. I had never done a big domain purchase before, so I reached out to a few domain brokers to understand the landscape. We tried different brokers, kept things anonymous, and attempted to surface a price the seller might consider. A year went by… nothing. Meanwhile, it was pretty clear this was only going to get more expensive as we grew. We needed a different approach. A fellow founder connected me to a broker who took a very different tack. Less transactional, more long-term relationship builder. He spent months getting to know the domain owner. Turns out owner was a fellow entrepreneur in the west coast… and a huge Grateful Dead fan. So we figured, why not get creative? Something beyond just price. So I called up our investor Ronny Conway and asked if there was any way he could help set up a private meeting between the domain owner and the Grateful Dead. Ronny is one of those people who somehow makes impossible things possible. A week later he calls me back: “New York City. Halloween. 15 minutes after the concert. Done.” The broker went back to the owner with an offer: some cash, some equity, and a private meeting with the Grateful Dead. That got his attention. He didn’t take the band meeting in the end, but he did lean into the equity (great call, in hindsight). We shook hands, and a few weeks later, the deal was done. I’ve been waiting years for the day we move our product to notion.com. Looks like 2026 is finally the year. Safe to say I’m unreasonably excited about this update!

I built a Notion Worker Custom Agent that takes whatever we post on @NotionHQ, localizes it, and schedules it to 3 regional X accounts (coming soon). One English post → ES, DE, PT versions. All drafted, reviewed, and scheduled in Sprout for the next morning. It’s a 5-step loop: 1. Router agent creates language pages the moment an HQ post goes live. 2. Translator agent drafts each version using translation glossary. 3. Human translator rewrites for tone cultural nuance. 4. Worker schedules everything in Sprout. 5. QA agent compares Original → Draft → Final and improves translation glossary. The system gets smarter with each run. Now, one local translator per market is enough to run product updates and educational content to 3 regions at ~ the same quality as HQ. Next: hiring SMM contractors in each region so the content feels local... same product heartbeat, but with local events, culture, and community.

What are you building today?

notion.

There is a truly unbelievable amount of noise and churn in the AI world. My hope for this new podcast is that we can bring a calm perspective to the AI hype topic du jour, grounded in the long history of computing.

🚀 @NotionHQ is my new agent orchestrator. Step 1: I write a plan for a change or a new feature thanks to the /grill-me @mattpocockuk skill Step 2: Change the status on Notion Step 3: A web server catches the event from Notion Step 4: Triggers an agent to make the job. No more coding! Just dragging and dropping specs from A to X. Y = QA Z = High Level code review

This weekend I’m putting @NotionDevs to build a smart mosquito and gnat repellant system in order to solve a problem plaguing suburban dads: Dad Sprawl — the slow accumulation of subscriptions in the pursuit of home excellence. I live in the DC area and the gnats and mosquitos are out of control. I pay 200/mo for a mosquito spraying service. It rains, it washes away, I pay again. I was quoted to upgrade to an "Evergreen” misting system quote: $8,600 $200/mo a $25 app. Respectfully: no. So I’m building the Mosquito & Gnat Destroyer System: Notion DB = the source of truth (schedule, rules, zones) a “Spray Commands” queue run logs Notion Worker (runs on a schedule) = reads the DB, checks weather/time, decides “spray vs skip,” and queues a command (zone seconds) Raspberry Pi = watches the command queue (or receives a request), flips a GPIO pin to trigger the relay/pump/valve, then marks the command/log as Done All-in, I’ve spent about $500 on equipment and supplies. Next I’ll cancel my $200/month service. Ongoing costs should be about $45/month for concentrate refills, plus roughly $1–$2/month in tokens to orchestrate everything in @NotionHQ (agent worker). Follow along the journey if interested!

Do you see yourself, or the smartest person you know, in this photo alongside @geoffreylitt @ivanhzhao @goldmanem and @_clem? Because we're hiring a developer advocate and it's an incredible role. You'd be building in public alongside @NotionDevs, and inspiring people around the 🌍 to create the Notion of the future. And we have an unlimited supply of Uncrustables. jobs.ashbyhq.com/notion/0cc3…

i had Claude Code build a Notion Worker that syncs SF's electronic music events into a Notion database with dates, venues, genres, prices, etc icymi you can sync any external data into Notion (for any use case)