Resources · Claude connector

Claude Superhuman Docs connectorWhat Claude can do in your Superhuman Docs account.

The Claude Superhuman Docs connector exposes 32 tools: 11 read, 21 write, 0 undocumented. Claude can build pages and tables, fill rows and comment, and also delete for good. Here: what your role in Docs allows, what you share at sign-in, and who can close it.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for the team that lives in Docs

Superhuman Docs, the product formerly known as Coda, mixes pages, tables and formulas in one document. With the connector, you describe the result you want and Claude does the clicking: it finds the right doc, reads its tables, adds the rows, rewrites a section or leaves a comment, working with the access you granted and the role you hold in Docs.

Turn meeting notes into a tracker. table_create builds a table with the columns you name, table_rows_manage fills it with the action items, and table_view_manage adds a filtered view per owner.

Answer a question from your own docs. search finds the relevant pages across workspaces, content_read reads them, and formula_execute computes a figure straight from a table.

Polish a rough draft. content_modify inserts, replaces or removes blocks in a page, and comment_add leaves a note for the author instead of silently rewriting.

Now, what the directory sheet does not say. Eight tools delete, a whole document included, and Superhuman writes that deleting a document cannot be undone. Signing in from Claude grants read and write together, with no narrower scope on that path. An Editor in Docs is limited to reading, whatever Claude asks. And nothing runs on its own: no tool wakes up when a row changes. Syncing a table with your CRM every night is a job for an automation tool; the Integrations hub covers that side.

Vocabulary

The vocabulary, in one minute

Five words you will run into while plugging Superhuman Docs in.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks what it needs as it answers, and the directory sheet lists every tool by name.
Authorization
The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and it can be taken back.
Approval
The confirmation Claude waits for before going ahead with something that changes your account, shown in the chat when it matters.
MCP
The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service such as Superhuman Docs.
Connect

Plug Superhuman Docs into Claude in three steps

  1. 01

    Find Superhuman Docs in Claude

    In Claude's settings, open Customize, then Connectors, and look for Superhuman Docs. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before any member can sign in.

  2. 02

    Start the connection

    Click Connect on its row and sign in to Superhuman Docs in the window it opens. If the link breaks later, use Disconnect, then plug the connector back in from the same row.

  3. 03

    Choose full or limited access

    Read the authorization screen before you accept: it belongs to Superhuman, not Claude. It asks for full access, or limited access to the workspaces and folders you pick. Take limited if Claude only needs one team's docs.

Tools

The 32 tools, sorted by what they do

Superhuman Docs gives Claude 32 tools: 11 that read your account, 21 that change something in it.

Eleven tools consult your docs, twenty-one change them. Names stay exactly as Claude shows them, in English.

  • 11 read
  • 21 write

What Claude reads (11)

11 tools

Eleven tools that look into your docs, tables and account without changing them.

tool_guide

Returns Superhuman's detailed guidance on a given area before Claude starts working in it. It is Claude reading the manual so the next step goes right.

When it helps
you ask for a tricky formula column and Claude wants the exact syntax first.

Sourcecoda.io · September 30, 2026 ↗

name_match

Takes an approximate page, table, view or person name and ranks the likely matches inside a document, by similarity.

When it helps
you say "the Q3 roadmap table" but the real title is "Roadmap, third quarter", and Claude needs the right one.

Sourcecoda.io · September 30, 2026 ↗

url_convert

Translates between the web address of a doc and the internal reference the tools use, in both directions. Paste a link from your browser and Claude knows exactly which page you mean.

When it helps
a colleague drops a Docs URL in the chat and asks what that page says.

Sourcecoda.io · September 30, 2026 ↗

document_outline

Returns a document's metadata (title, owner, creation date) and the list of its pages with sub-pages, page by page. It maps the structure without reading the body text.

When it helps
before restructuring a sprawling wiki, you want the tree of pages in front of you.

Sourcecoda.io · September 30, 2026 ↗

page_describe

Reads the metadata of one page: title, type, hidden or not, parent, position, icon, cover, subtitle, authors and timestamps. The content itself stays for another tool.

When it helps
you need to know who last touched a policy page and when.

Sourcecoda.io · September 30, 2026 ↗

content_read

Reads the body of a page, or of a canvas stored inside a table cell, so Claude can summarise, quote or check it against another source.

When it helps
a sales rep wants the pricing section of the internal playbook boiled down before a call.

Sourcecoda.io · September 30, 2026 ↗

table_columns_read

Returns a table's column schema: names, IDs, whether each column is writable, its format and any formula, plus the row count. Claude checks this before touching rows.

When it helps
you are about to import data and want to know which columns are calculated and cannot be filled.

Sourcecoda.io · September 30, 2026 ↗

table_rows_read

Fetches rows with their cell values from a table, which is what Claude works from when you ask about the data itself.

When it helps
a project manager wants every task marked blocked in the sprint table, with its owner and due date.

Sourcecoda.io · September 30, 2026 ↗

formula_execute

Runs an expression in Coda Formula Language against a document and returns the result, without adding the formula anywhere.

When it helps
finance wants the count of unpaid invoices over a threshold, straight from the ledger table.
Watch out
it needs a document reference to run.

Sourcecoda.io · September 30, 2026 ↗

whoami

Returns the signed-in user's ID, name and email, along with the workspaces they belong to. It tells Claude which account and workspaces it is working in.

When it helps
you ask for every row assigned to you across the team tracker.

Sourcecoda.io · September 30, 2026 ↗

What Claude changes (21)

21 tools

Twenty-one tools that create, edit or delete. No source describes a confirmation of their own: the general rule further down applies.

document_create

Approval: see the rule

Starts a brand-new document in your workspace, the blank canvas the page and table tools then fill in.

What Claude asks for
no confirmation specific to this tool is documented, so the general approval rule governs it.
When it helps
a new client project needs its own doc before the kickoff call.

Sourcecoda.io · September 30, 2026 ↗

document_delete

Approval: see the rule

Removes an entire document permanently. Superhuman states plainly that this cannot be undone.

What Claude asks for
nothing specific is documented for this one; look to the general approval rule below.
When it helps
a test doc from a training session clutters the workspace.
Watch out
name the exact document; there is no recycle bin mentioned.

Sourcecoda.io · September 30, 2026 ↗

page_create

Approval: see the rule

Creates a new page inside a document. Copying an existing page is a different tool.

What Claude asks for
sources say nothing about a prompt here, so the approvals section covers it.
When it helps
each client in a handbook needs its own sub-page.

Sourcecoda.io · September 30, 2026 ↗

page_update

Approval: see the rule

Updates an existing page in a document. The source says no more than that, so ask Claude to tell you what it plans to change.

What Claude asks for
no source spells out a confirmation for page updates; the general rule applies.
When it helps
a team wiki page needs refreshing before it is shared company-wide.

Sourcecoda.io · September 30, 2026 ↗

page_delete

Approval: see the rule

Deletes a page from a document, and optionally all its child pages along with it.

What Claude asks for
the documentation is silent on a prompt for this tool, so rely on the approval rules below.
When it helps
last year's event pages are obsolete and clutter the navigation.
Watch out
the recursive option takes the whole branch.

Sourcecoda.io · September 30, 2026 ↗

content_modify

Approval: see the rule

Inserts, replaces or deletes elements inside a page's body, and can make headings or tables collapsible.

What Claude asks for
no tool-level confirmation is described; the default approval behavior is what protects you.
When it helps
a rough draft needs a clean structure and a rewritten intro.

Sourcecoda.io · September 30, 2026 ↗

content_duplicate

Approval: see the rule

Copies pages or whole documents into a new or an existing document.

What Claude asks for
Superhuman describes no prompt of its own for copies; the general approval rule is the one in force.
When it helps
every new hire gets a copy of the onboarding page in their personal doc.

Sourcecoda.io · September 30, 2026 ↗

content_image_upload

Approval: see the rule

Uploads an image into a page placeholder, or prepares an upload link so an image can go into a table cell.

What Claude asks for
nothing is documented beyond the general approval rule.
When it helps
a product catalogue table needs its photos filled in.

Sourcecoda.io · September 30, 2026 ↗

table_create

Approval: see the rule

Creates a table on a page with the columns you specify, and optional starting data.

What Claude asks for
no specific prompt is described for new tables; see the approvals section.
When it helps
a hiring manager wants a candidate tracker with stage, date and owner columns.

Sourcecoda.io · September 30, 2026 ↗

table_delete

Approval: see the rule

Removes a whole table from a document, with all of its data, permanently.

What Claude asks for
sources describe no dedicated confirmation; the default rule is your safeguard.
When it helps
a deprecated tracker was replaced months ago and still confuses people.

Sourcecoda.io · September 30, 2026 ↗

table_columns_manage

Approval: see the rule

Adds columns to a table or updates the name, type or formula of the ones already there, so the structure follows what the team now tracks.

What Claude asks for
no confirmation of its own is documented, so the general rule decides.
When it helps
a budget table needs a calculated margin column.

Sourcecoda.io · September 30, 2026 ↗

table_columns_delete

Approval: see the rule

Removes one or several columns from a table, along with the values they held.

What Claude asks for
the documentation mentions no prompt for column removal; the approval rules below apply.
When it helps
a CRM-style table carries five fields nobody has filled in a year.

Sourcecoda.io · September 30, 2026 ↗

table_rows_manage

Approval: see the rule

Inserts new rows or updates existing ones, depending on the action Claude picks.

What Claude asks for
no row-level confirmation is documented; the general approval rule covers it.
When it helps
twenty action items from a workshop must land in the team tracker.

Sourcecoda.io · September 30, 2026 ↗

table_rows_delete

Approval: see the rule

Removes rows from a table, for example in bulk once tasks are closed.

What Claude asks for
no confirmation specific to row deletion is described, so it falls under the default rule.
When it helps
a support table keeps hundreds of resolved tickets nobody reads.
Watch out
check the filter before a bulk removal.

Sourcecoda.io · September 30, 2026 ↗

table_view_manage

Approval: see the rule

Adds a view to a table or configures an existing one: layout (charts included), filters, sorts, groups, visible columns, column order and conditional formatting.

What Claude asks for
sources say nothing of a prompt for views; the general rule applies.
When it helps
each regional manager wants a view showing only their accounts.

Sourcecoda.io · September 30, 2026 ↗

table_view_delete

Approval: see the rule

Removes one view of a table. The underlying table and its data stay in place.

What Claude asks for
no dedicated confirmation is documented; see the approval rules further down.
When it helps
a dozen personal views pile up under a shared table and nobody knows which ones matter.

Sourcecoda.io · September 30, 2026 ↗

control_manage

Approval: see the rule

Creates or updates a control on a page: a formula, a button or a reaction.

What Claude asks for
nothing specific is documented; the default approval behavior applies.
When it helps
a dashboard page needs a running total displayed at the top.

Sourcecoda.io · September 30, 2026 ↗

control_delete

Approval: see the rule

Removes a control from a document permanently, whether formula, button or reaction.

What Claude asks for
Superhuman documents no prompt for this; the general approval rule is what stands in the way.
When it helps
an old dashboard still shows a formula based on a table that no longer exists.

Sourcecoda.io · September 30, 2026 ↗

comment_add

Approval: see the rule

Adds a comment, a reply or an emoji reaction on a page element, a table row, a thread or a specific comment.

What Claude asks for
no source describes a confirmation for comments; the general rule applies.
When it helps
Claude reviews a proposal and you want its remarks left as comments, not edits.

Sourcecoda.io · September 30, 2026 ↗

comment_resolve

Approval: see the rule

Marks a comment thread as resolved, or reopens one that was already closed.

What Claude asks for
no confirmation specific to resolving is documented, so the approvals section covers it.
When it helps
after a round of fixes, thirty feedback threads can be closed in one pass.

Sourcecoda.io · September 30, 2026 ↗

comment_delete

Approval: see the rule

Permanently removes a single reply, or an entire comment thread.

What Claude asks for
nothing beyond the general approval rule is described.
When it helps
a comment with a pasted password has to disappear from a shared doc.
Watch out
deleting a thread takes every reply in it.

Sourcecoda.io · September 30, 2026 ↗

Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before each action it takes on an account in your place. The request shows up in the conversation, right when it matters.

With twenty-one write tools, eight of them deletions, that default carries real weight here. On a Team or Enterprise workspace, owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reads and closing writes, and nobody overrides that from their own account. Finally, Claude works with your rights and nothing more: a doc you cannot open stays closed to it.

Plans

Which plans it works on

Out of 819 sheets in the official directory, none shows availability plan by plan. The answer for a given connector is published nowhere.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members can connect. Superhuman's own subscription is a separate matter, covered under limits. For the current state of this connector, check its sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a row changes or a page gets edited.

The tool list is an observed floor, not a promise: an admin can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic writes on every sheet that it neither picks a publisher's tools nor vouches for how they behave. Everything here comes from Superhuman's help article and its tool reference, since neither Claude's help center nor Anthropic's developer docs cover it. For another connector page, see the Claude airtable connector.

Need help

Need help connecting Superhuman Docs to Claude?

A person reads every message.

FAQ

Claude Superhuman Docs connector: frequent questions

01What can Claude do with the Superhuman Docs connector?
Claude can read and build your docs from the chat. Eleven tools read: search across docs, outlines, page details and content, table schemas and rows, formula results, name matching, link conversion, guidance and your user identity. Twenty-one tools act: they create and delete documents, pages, tables, columns, rows, views and controls, edit page content, duplicate pages, upload images, and add, resolve or delete comments. What you can use depends on your role in Docs.
02Can Claude write or delete things in Superhuman Docs?
Yes, and some of it is permanent. Twenty-one documented tools change your docs, and eight delete: a document, a page, a table, its columns or rows, a view, a control or a comment. Superhuman states that deleting a document cannot be undone. Writing requires the right role: an Editor in Docs only gets the read tools. Signing in from Claude grants read and write together, with no read-only option on that path.
03Does Claude ask before changing my docs?
By default, yes: Claude asks for confirmation before each action it takes on an account in your place. No source describes a confirmation specific to a Superhuman Docs tool, so that rule covers creation, edits and deletions alike. With eight delete tools on the list, read each request before you approve it. On a Team or Enterprise workspace, owners decide whether members can skip some prompts, and they can close writes for everyone.
04Which plans is the Superhuman Docs connector available on?
No official source publishes plan-by-plan availability for each connector, and no directory sheet shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on first; Superhuman adds that a missing Connect button usually means that step is pending. The directory sheet shows the current state for your account.
05Does Claude see every doc in my workspace?
Only what your access covers. At sign-in, Superhuman lets you grant full access or limited access to chosen workspaces and folders, and Claude then stays inside them. Your role matters too: an Editor gets read tools only. Claude always works with your rights and nothing beyond them, and a Team or Enterprise owner can restrict what the connector may do across the whole organization, a setting that no member can lift alone.
06Why can Claude read my docs but not edit them?
Most likely because your role in Docs is Editor. Superhuman's help article says Editors are limited to the read tools and cannot add or update content through the connector; editing takes a Doc Maker account. Another possible cause is a request allowance: a Doc Maker without a paying Superhuman Docs subscription gets 30 requests per week, 60 per month at most. Your organization's Claude owner may also have closed writes.
07Claude or an automation tool for Superhuman Docs?
They cover different needs. Claude works in a conversation: you ask, it reads, builds or edits a doc, then nothing happens once you stop typing. It does not react on its own when a row changes or a form is submitted. Syncing a table with another app every night, or alerting a channel on a status change, is a job for an automation tool. For writing, restructuring and answering questions from your docs, the connector fits.