Anthropic Software / SaaS North America

Notion

Enterprise Knowledge Search · IT Operations Automation

Notion needed to embed trusted Claude agents natively inside collaborative workflows, with automations, long-running tasks, memory, coding sandboxes, and human approvals that could scale across whole workspaces instead of one-user/one-agent chats.

12 hours of prototyping work collapse into about 20 minutes
18,000 Claude agents created in the first three weeks
90% of agent turns triggered by automations, not chat
about 140,000 steps

Reported impact

Business outcome

Notion created 18,000 Claude agents in the first three weeks, saw 90 percent of agent turns come from automations rather than chat, and reduced early prototyping work from about 12 hours to 20 minutes while keeping agent collaboration and permissions inside the existing workspace.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Notion built External Agents on Claude Managed Agents so Claude sessions can live inside Notion pages and task boards rather than separate tools. A Notion task board acts as the orchestrator: moving a task to ready-to-start invokes a Claude session that pulls context from connected pages, design systems, API docs, and product requirements documents. Most usage is automated, triggered by Notion pages, Slack messages, or schedules, and top workspaces run several agents across dozens of threads per day. Managed Agents supplies the long-running execution layer, memory, sandbox, packages, and GitHub endpoint that let Claude read repositories and run code. Notion also splits work across stage-specific agents—investigate, plan, build—with different permissions and sharing rules so collaborative teams can review and approve work safely inside the same workspace.

Data flow

Pages, task boards, Slack messages, or schedules trigger a Claude session inside Notion; the session pulls context from connected documents and repositories, performs the requested work, and streams results back as files, comments, or page updates that teammates can review and approve.

Solution architecture

1 components · 1 layer
  1. Orchestration
    • Claude Managed Agents Provides the hosted execution, memory, sandbox, and API building blocks behind Notion's embedded Claude sessions.

Architecture clues

  • A Notion task board acts as an orchestrator for Claude sessions.
  • Notion deploys separate investigator, planner, and builder agents with distinct permissions.
  • Top workspaces run three or four agents across dozens of threads per day.

Evidence from the source

90% of the turns people are doing with Claude are automations in Notion, triggered on a Notion page, a Slack message, or scheduled runs.
Even with the early prototype, we saw 12 hours of prototyping work collapse into about 20 minutes.
So far it's about 18,000 Claude agents created, and those agents have done about 140,000 steps.
The GitHub endpoint in Managed Agents was really useful.
You create a task, move it to "ready to start," and it invokes a Claude session.
Transparency Evidence & methodology 100/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Anthropic

    Notion customer story

    First-party
    https://claude.com/customers/notion-qa
    Source type
    Vendor-published customer story
    Published
    Aug 21, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Publisher catalog date Aug 21, 2026 · Anthropic · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.