Sanaf AI
Start free
Productivity

Coda, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Coda account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Productivity
  • Connects with a key
  • 100 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Coda is

Collaborative workspace platform that transforms documents into powerful tools for team productivity and project management

You paste in a key from your own Coda account. It is kept encrypted, and you can withdraw it from inside Coda whenever you like.

It can also be told by Coda when something happens, rather than only doing things when you ask.

How a run works

One message in, the work done in Coda.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Coda. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Coda account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

100 tools it already has

What it can do in Coda

These are the ready-made tools your AI employee already has in Coda. It is not limited to them, but it never has to be taught these.

  • Add a category for packAdd a publishing category for a given pack.
  • Add a maker for packSet a maker for a given pack. used to display makers for a pack in the corresponding packs page.
  • Add a permission for packCreate or modify user, workspace, or global permissions for a given pack.
  • Add custom domainAdd a custom domain to a published doc.
  • Add permissionAdds a new permission to the doc.
  • Begin content exportInitiate an export of content for the given page.
  • Content export statusCheck the status of a page content export
  • Copy DocumentCreates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.
  • Create a new pack releaseCreates a new pack release based on an existing pack version.
  • Create a pageCreate a new page in a doc. note that creating a page requires you to be a doc maker in the applicable workspace.
  • Create docCreates a new coda doc, optionally copying an existing doc. note that creating a doc requires you to be a doc maker in the applicable workspace (or be auto-promoted to one).
  • Create packCreates a new pack, essentially registering a new pack id. the contents of the pack will be uploaded separately.
  • Delete a category for packDelete a publishing category for a given pack.
  • Delete a maker for packDelete a maker for a given pack, who will not be displayed in the corresponding packs page.
  • Delete a pageDeletes the specified page.
  • Delete a permission for packDelete user, workspace, or global permissions for a given pack.
  • Delete docDeletes a doc.
  • Delete multiple rowsDeletes the specified rows from the table or view. this endpoint will always return a 202. row deletions are generally processed within several seconds.
  • Delete packDelete a given pack.
  • Delete permissionDeletes an existing permission.
  • Delete rowDeletes the specified row from the table or view. this endpoint will always return a 202, so long as the row exists and is accessible (and the update is structurally valid). row de
  • Deletes a custom domainDeletes a custom domain from a published doc.
  • Fetch grouped logs by pack org root ingestion idRetrieve the grouped logs of a pack for debugging purpose.
  • Fetch ingestion executions for packRetrieve the ingestion execution ids of a root ingestion for debugging purpose.
  • Get a columnReturns details about a column in a table.
  • Get a controlReturns info on a control.
  • Get a formulaReturns info on a formula.
  • Get a pageReturns details about a page.
  • Get a rowReturns details about a row in a table.
  • Get a single packReturns a single pack.
  • Get a tableReturns details about a specific table or view.
  • Get acl settingsReturns settings associated with acls for this coda doc.
  • Get analytics last updated dayReturns days based on pacific standard time when analytics were last updated.
  • Get detailed listing information for a packGet detailed listing information for a pack.
  • Get doc analytics summaryReturns summarized analytics data for available docs.
  • Get doc categoriesGets all available doc categories.
  • Get info about a docReturns metadata for the specified doc.
  • Get mutation statusGet the status for an asynchronous mutation to know whether or not it has been completed. each api endpoint that mutates a document will return a request id that you can pass to th
  • Get pack analytics summaryReturns summarized analytics data for packs the user can edit.
  • Get sharing metadataReturns metadata associated with sharing for this coda doc.
  • Get the difference between two pack versionsGets information about the difference between the specified previous version and next version of a pack.
  • Get the next valid version for a packGet the next valid version based on the proposed metadata.
  • Get the source code for a pack versionGet temporary links used to download the source code for the given packid and version
  • Get user infoReturns basic info about the current user.
  • Gets custom doc domains providersGets the provider (ie. godaddy) of a custom domain.
  • Gets the json schema for pack configurationReturns a json schema applicable for customizing the pack using pack configurations.
  • List available docsReturns a list of coda docs accessible by the user, and which they have opened at least once. these are returned in the same order as on the docs page: reverse chronological by the
  • List categories for packList publishing categories for a given pack.
  • List columnsReturns a list of columns in a table.
  • List controlsReturns a list of controls in a coda doc.
  • List custom doc domainsList all custom domains for a published doc.
  • List doc analyticsReturns analytics data for available docs per day.
  • List featured docs for a packReturns a list of featured doc ids for a pack.
  • List formulasReturns a list of named formulas in a coda doc.
  • List makers for packList makers for a given pack.
  • List pack analyticsReturns analytics data for packs the user can edit.
  • List pack formula analyticsReturns analytics data for pack formulas.
  • List packsGet the list of accessible packs.
  • List page analyticsReturns analytics data for a given doc within the day. this method will return a 401 if the given doc is not in an enterprise workspace.
  • List pagesReturns a list of pages in a coda doc.
  • List permissionsReturns a list of permissions for this coda doc.
  • List permissions for a packGet user, workspace, and/or global permissions for a given pack.
  • List table rowsRetrieves rows from a specific table within a coda document. this endpoint allows you to fetch data from your coda tables programmatically, enabling integration with other systems
  • List tablesReturns a list of tables in a coda doc.
  • List the pack listings accessible to a userGet listings of public packs and packs created by you.
  • List the releases for a packGet the list of releases of a pack.
  • List the versions for a packGet the list of versions of a pack.
  • List workspace rolesReturns a list of the counts of users over time by role for the workspace.
  • List workspace usersReturns a list of members in the given workspace. this list will be ordered with the requesting user first and then ordered by role.
  • Pack asset upload completeNote the completion of the upload of a pack asset.
  • Pack source code upload completeNote the completion of the upload of a pack source code.
  • Pack version upload completeNote the completion of the upload of a pack version bundle in order to create that pack version.
  • Patch the system connection credentials of the packPatch the system connection credentials of the pack.
  • Publish docUpdate publish settings for a doc.
  • Push a buttonPushes a button on a row in a table. authorization note: this action is available to api tokens that are authorized to write to the table. however, the underlying button can perfor
  • Register pack versionRegisters a new pack version. this simply returns a signed url to use for uploading the pack version definition. following the completion of the upload, post to /apis/v1/packs/{pac
  • Resolve browser linkGiven a browser link to a coda object, attempts to find it and return metadata that can be used to get more info on it. returns a 400 if the url does not appear to be a coda url or
  • Retrieve the grouped logs of a packRetrieve the grouped logs of a pack for debugging purpose.
  • Retrieve the information for a specific logRetrieve the ingestion execution ids of a root ingestion for debugging purpose.
  • Retrieve the logs of a ingestionRetrieve the logs of a ingestion for debugging purpose.
  • Retrieve the logs of a packRetrieve the logs of a pack for debugging purpose.
  • Retrieve the oauth configuration of the packRetrieve the oauth configuration of the pack for display purpose. secrets will be returned with masks.
  • Retrieve the system connection metadata of the packRetrieve the system connection metadata of the pack.
  • Search Coda DocumentsThis tool allows users to search for coda documents based on a query term. it searches within document titles and metadata, providing results with document id, name, type, owner de
  • Search principalsSearches for user and group principals matching the query that this doc can be shared with. at most 20 results will be returned for both users and groups. if no query is given then
  • Search Table RowsAction to search for rows in a coda table based on specific criteria.
  • Set the oauth configurations of the packSet the oauth configurations of the pack, including client id and secret.
  • Set the system connection credentials of the packSet the system connection credentials of the pack.
  • Trigger automationTriggers webhook-invoked automation
  • Unpublish docUnpublishes a doc.
  • Update a pageUpdate properties for a page. note that updating a page title or icon requires you to be a doc maker in the applicable workspace.
  • Update acl settingsUpdate settings associated with acls for this coda doc.
  • Update an existing pack releaseUpdate details of a pack release.
  • Update docUpdates metadata for a doc. note that updating a doc title requires you to be a doc maker in the applicable workspace.
  • Update featured docs for a packCreate or replace the featured docs for a pack.
  • Update packUpdate an existing pack for non-versioned fields.
  • Updates a custom domainUpdates properties of a document's custom domain.
  • Updates user roleUpdates the workspace user role of a user that matches the parameters. only succeeds if the requesting user has admin permissions in the workspace.
  • Upload a pack assetRequest a signed s3 url to upload your pack asset.
  • Upload pack source codeRequest a signed s3 url to upload your pack source code.
4 things it can watch for

What Coda can tell it about

It does not only wait to be asked. These are the things Coda can tell your AI employee about the moment they happen, so it can act without anyone noticing first.

  • Coda Document Deleted TriggerA Coda document is deleted.
  • New Coda Document TriggerA new Coda document is created.
  • New Coda Page TriggerA new page is added to a Coda document.
  • Specific Coda Page Updated TriggerA specific page within a Coda document is updated.
Access, and who is in charge of it

You stay the boss of your Coda account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Coda account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Coda is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Coda and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Coda

Can an AI employee really work inside Coda?
Yes. It signs in to your own Coda account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Coda?
No. Nothing moves and nothing is replaced. Your records stay in Coda, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Coda account?
You paste in a key from your own Coda account. It is kept encrypted, and you can withdraw it from inside Coda whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Coda?
It has 100 ready-made tools in Coda today, among them Add a category for pack, Add a maker for pack and Add a permission for pack. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Coda and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Coda and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Coda?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Coda is written down with what it did and when.