Skip to main content
The Coda integration makes your team’s docs and trackers available in client work. Ask what the Contoso kickoff page says about scope, pull the open rows from a risk tracker table, or add a finished interview summary as a new page. Hebno cites each page and row it reads, and writes to Coda only after you confirm.

​
At a glance

​
Before you start

You need:
  • A Coda account that can open the docs you want to use, with edit access on docs where you want Hebno to add pages or rows.
  • An allowed integration. An owner or admin sets Coda to Allow under Admin → Connectors → Catalogue.
  • A Coda API token. In Coda, open Account settings, scroll to API settings and select Generate API token.
A Coda API token has the access of the user who creates it. When you create the token, you can restrict it: If your Coda workspace admin turns off API access for members, tokens stop working. Ask them to allow it in the workspace settings.

​
Connect Coda

1

Check the integration is allowed

An owner or admin controls this under Admin → Connectors → Catalogue. If Coda shows Blocked, ask an admin to set it to Allow.
2

Create a token in Coda

In Coda, open Account settings → API settings, select Generate API token, name it Hebno, choose the access and copy the token.
3

Connect in Hebno

Open Settings → Connections, find Coda under Knowledge, select Connect, paste the token and select Connect. The row shows Connected with your Coda name.
Hebno stores the token encrypted at rest. To revoke it, delete it in Coda under API settings, or select Disconnect in Hebno. Admins can revoke any member’s connection from Admin → Connectors → Connections.

​
What Hebno reads

The docs your organisation selects are stored in the knowledge index and searched by meaning, with Coda permissions checked at search and again at read. Opening a specific page or table reads it as it is now, with your token. Only the excerpts a reply used are stored with the conversation as its sources. To filter a table, Hebno queries its rows by column value, for example status or owner, rather than reading the whole table.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, even if they cannot open the doc in Coda.

​
What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Coda with editable fields

A Coda change pending confirmation. Nothing is written until you confirm.

Formula columns and Pack sync tables are calculated in Coda, so they are read only on the card. Coda processes writes in a queue, so a new row or page can take a few seconds to appear. Hebno never deletes or edits existing pages and rows, changes formulas, presses buttons or changes sharing. Linking marks which Coda docs belong to an engagement, so you can ask “what is on the risk tracker?” without naming the doc.
  1. Open the project and select Brain.
  2. Under Linked sources, select Link source, then Coda.
  3. Search by doc name, or paste a Coda doc link, and select Link.
In chats tagged to the project, Hebno searches the linked docs first, and page and row cards default to them. Each person still reads the doc with their own Coda access. See Linked records.

​
Use Coda in chat

  • Attach: open the + menu, choose Sources → Coda, and pick a doc, a page or a table. Or type / and choose Coda.
  • Ask: name the doc, page or table in your request. For example:
    List every open risk on the Contoso risk tracker, grouped by owner, with due dates in November 2026.
    Summarise the Contoso kickoff page and the decision log table for the steering committee update.
    Add the interview with Sarah Chen to the Interviews table, dated 4 November, status Complete.
  • Research runs show a Reviewing Coda step, with a chip for each page and table Hebno read.
  • Agents can read Coda on a schedule, for example a Monday summary of open risks. Writes an agent proposes appear in agent approvals for review.

​
Troubleshooting