Integration · Automate and collaborate

Coda and Meteor AI agents

Connect Coda (now Superhuman Docs) to a WhatsApp Met: read price or stock tables, add rows and leave comments through the official MCP server.

Book a demo See every integration

How does Coda connect to Meteor?

Coda is now called Superhuman Docs, and with its ready connector your WhatsApp Met reads and writes in your company's docs with the permissions of the account the admin authorizes. It finds a doc, locates its tables and reads the rows it needs, so it answers about a price, stock or opening hours with what your team wrote in the doc, not from memory. If the admin leaves writing on, it also adds or updates rows, such as a new order, and leaves comments for your team. These are 32 tools from the official server: usage runs on your Superhuman Docs plan, and delete actions start switched off until the admin turns them on.

What it automates

What a Meteor Met does with Coda

Answer with the price or stock table that lives in a doc

When a customer asks how much something costs or whether it is in stock, your Met locates the table in the doc, reads its columns and brings the product's row with a filter. If your team changes the price in the doc, the next answer already uses the new price.

Log an order or a request as a new row

If the admin leaves writing on, the Met adds a row to the orders or requests table with what the person asked for, and updates it later if the customer changes the quantity or the address.

Alert the team with a comment on the row

The Met leaves a comment on the order row or on the customer page so the person in charge sees it in Superhuman Docs, with a summary of what was said on WhatsApp.

Count or add up with a doc formula

For team questions such as how many orders are still pending or what a table's sales add up to, the Met evaluates a Coda formula on the doc and answers with the result.

32 tools

Everything your Met can ask Coda for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`search`	Searches docs, pages, rows, folders or people, or lists recent docs, up to 10 results per query.
`whoami`	Returns the user who authorized the connection, with their name, email and workspaces.
`tool_guide`	Returns usage guidance on a topic, such as tables, pages, formulas or comments, before working on it.
`name_match`	Finds pages, tables, views or people in a doc from an approximate name, up to 20 per call.
`url_convert`	Converts the link to a doc, page, table or row into the ID the other tools use, and back.
`document_create`	Creates a new doc in the connected account's workspace.
`document_delete`	Deletes a doc permanently, with no way back. It starts switched off.
`document_outline`	Shows a doc's structure, with its title, owner, pages and subpages, up to 50 per call.
`page_create`	Creates a new page inside a doc.
`page_update`	Updates a page that already exists in a doc.
`page_delete`	Deletes a page from a doc and, if requested, its subpages too. It starts switched off.
`page_describe`	Returns a page's details, such as title, type, whether it is hidden, position, icon and authors.
`content_read`	Reads the content of a page or a rich text cell, and can search for text inside it.
`content_modify`	Inserts, replaces or deletes elements in a page's content.
`content_duplicate`	Copies pages or docs into a new doc or an existing one.
`content_image_upload`	Uploads an image from an https link to a page, or prepares the upload for a table image cell.
`table_create`	Creates a table on a page with its columns and, optionally, initial data.
`table_delete`	Deletes an entire table with all its data. It starts switched off.
`table_columns_read`	Reads a table's columns, with their name, type, whether they are writable, formulas and the row count.
`table_columns_manage`	Adds columns to a table or changes their name, type or formula.
`table_columns_delete`	Deletes columns from a table. It starts switched off.
`table_rows_read`	Reads rows from a table or a view, with a formula filter, up to 100 rows per call.
`table_rows_manage`	Adds rows to a table or updates existing ones, up to 100 new rows per call.
`table_rows_delete`	Deletes rows from a table. It starts switched off.
`table_view_manage`	Creates or configures a table view, with filters, sorting, groups, charts and visible columns.
`table_view_delete`	Deletes a table view. It starts switched off.
`formula_execute`	Evaluates a Coda formula on a doc and returns the result, for example a count or a sum. It starts switched off.
`control_manage`	Creates or updates a control on a page, such as a button, checkbox, slider or date picker.
`control_delete`	Deletes a control from a doc permanently. It starts switched off.
`comment_add`	Adds a comment, a reply or a reaction on a page, a table row or a thread.
`comment_resolve`	Marks a comment thread as resolved or reopens it.
`comment_delete`	Permanently deletes a reply or an entire comment thread. It starts switched off.

The limits

What the Coda integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask for confirmation in the chat before writing to a doc. The admin chooses in Connections which actions stay on; delete actions start switched off.
It does not go beyond the connected account's permissions. If that account can only view a doc, the Met reads it but does not change it; if it can edit, it can also delete pages, rows, columns and tables when those actions are on.
It does not edit a locked table. Superhuman blocks MCP changes on locked tables, except for the actions the lock settings allow, such as adding rows. Locking is on the Team and Enterprise plans.
It does not write to formula or reaction columns: the doc calculates those. It only fills the columns the table marks as writable.
It does not bring long lists at once: search returns up to 10 results and reading a table up to 100 rows per call.
It does not recover what it deletes. According to Superhuman, deleting a doc, a table, a control or a comment this way is permanent.

Before you start

What you need to connect Coda

1

A Superhuman Docs (formerly Coda) account with access to the docs the Met will use

The connector acts as that account: whatever it cannot open or change, the Met cannot either. To log orders, the account needs edit access to that doc.
2

The Superhuman Docs plan that covers the usage

According to Superhuman, a Doc Maker on a paid plan uses every tool. A Doc Maker on the free plan gets a trial of 30 requests per week, with a maximum of 60 per month, and an editor gets the same trial but only with the read tools.
3

Connect it in Met

In Met, open Connections → Coda (Superhuman Docs) → Connect. A Superhuman Docs window opens so you can sign in, choose whether the connection sees everything or only certain workspaces or folders, and accept. Then you choose which actions stay on.

Frequently asked questions

Questions about Coda and Meteor

Yes. Coda was renamed Superhuman Docs and its MCP server was renamed too. The connector uses the new server, which according to Superhuman is the one that gets new features; the old Coda MCP still works for now, but it will be retired.

The same ones the authorizing account can see. When you authorize, you can give it limited access to certain workspaces or folders, and the Met will only see the docs in them.

Lock that table in the doc: Superhuman does not allow MCP edits on a locked table. You can also give the connected account read only access to the price doc.

For a trial. The free plan gives 30 requests per week and a maximum of 60 per month, which falls short for a WhatsApp line with daily traffic. For real use, a paid plan is the better fit.

You do, with your own Superhuman Docs plan. Meteor does not resell the service: the connector uses your company's account and follows the limits Superhuman sets for that account.

Step by step