Coda for AI agents
Agents read Coda at once. Changes and sends are held for a person's approval by default.
About Coda
Collaborative workspace platform that transforms documents into powerful tools for team productivity and project management
What an agent can do in Coda
Every Coda action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Coda without asking first. 56 actions.
- List the pack listings accessible to a userGet listings of public Packs and Packs created by you.
- Begin content exportInitiate an asynchronous export of page content in HTML or Markdown format. This action starts a content export job and returns immediately with a request ID and status URL. The export is processed as
- Content export statusCheck the status of a page content export operation. Use this to poll the export status and retrieve the download link when the export completes.
- Get acl settingsReturns settings associated with ACLs for this Coda doc.
- Get a columnReturns detailed information about a specific column in a Coda table. Retrieves column metadata including: - Column ID, name, type, and href - Format details (type, isArray, label, action, displayType
- Get a controlReturns info on a control.
- Get a formulaReturns info on a formula.
- Get analytics last updated dayReturns days based on Pacific Standard Time when analytics were last updated.
- Get a pageReturns details about a page.
- Get a rowRetrieves detailed information about a specific row in a Coda table, including all cell values, metadata (creation/update timestamps), and parent table information. Use this action when you need to re
- Get Pack details by IDRetrieves detailed information about a specific Coda Pack by its ID. Returns pack metadata including name, description, workspace, logo URL, categories, rate limits, and configuration settings. Only a
- Get a tableReturns details about a specific table or view.
Show all 56
- Get detailed listing information for a packGet comprehensive public listing information for a Coda Pack. Returns detailed metadata about a Pack including its description, logo, categories, makers, pricing, version information, and user access
- Get doc analytics summaryReturns aggregated analytics summary data across documents, including session counts, installs, copies, reads, and conversions. Can be filtered by publication status, date range, and workspace.
- Get doc categoriesRetrieves the list of all available doc categories in Coda. These categories can be used when publishing docs to help users discover content.
- Get folderTool to get metadata about a Coda folder. Use when you need to retrieve information about a specific folder including its name, description, icon, workspace, and editing permissions.
- Get info about a docRetrieves comprehensive metadata for a specific Coda document. This action returns detailed information about a document including its name, owner, creation/update timestamps, workspace and folder loc
- Get mutation statusChecks whether an asynchronous mutation operation has been applied to a Coda document. When you perform mutations like inserting/updating rows, deleting rows, or pushing buttons, the Coda API returns
- Get pack analytics summaryReturns summarized analytics data for Packs the user can edit. This endpoint provides aggregate statistics including: - Total Pack invocations across all accessible Packs - Total document installation
- Gets custom doc domains providersIdentifies the domain registrar/provider for a given domain name by performing a DNS lookup. Returns the provider name (e.g., GoDaddy, Namecheap) or 'Other' if unidentified. Useful for determining whe
- Get sharing metadataReturns metadata associated with sharing for this Coda doc.
- Gets the json schema for pack configurationRetrieves the JSON Schema that defines the configuration options available for a specific Coda Pack. This schema describes how the Pack can be customized, including connection settings, OAuth scopes,
- Get the difference between two pack versionsGets information about the difference between the specified previous version and next version of a Pack. This endpoint compares two semantic versions of a Pack and returns the differences. Both versio
- Get the next valid version for a packGet the next valid version number for a Pack based on the proposed metadata. This endpoint validates the proposed Pack metadata and determines what the next semantic version number should be. It retur
- Get the source code for a pack versionRetrieves temporary download URLs for the source code files of a specific Pack version. Returns pre-signed, time-limited URLs to download the original TypeScript/JavaScript source code. Useful for rev
- Get user infoReturns basic info about the current user.
- 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 latest event releva
- List categories for packList all publishing categories associated with a specific Coda Pack. Categories help users discover packs by organizing them into topics like 'Project Management', 'Marketing', 'Engineering', etc.
- 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 configured for a published Coda doc. Custom domains allow you to publish your doc at your own domain (e.g., www.example.com) instead of the default Coda.io URL. Returns an empt
- List doc analyticsReturns analytics data for accessible documents. Provides detailed metrics including views, sessions (desktop/mobile/other), copies, likes, and AI credits usage. Supports filtering by workspace, date
- List featured docs for a packReturns a list of featured docs for a Pack. Featured docs are example or template documents that showcase how to use the Pack. Each entry includes the document reference (id, type, href, browserLink),
- List FoldersTool to list folders accessible by the user. Returns a list of folders with their metadata including ID, name, workspace, and icon. Use when you need to discover available folders or find a specific f
- 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. This endpoint retrieves analytics information for Packs where the authenticated user has edit permissions. Analytics include installation counts, in
- List pack formula analyticsReturns analytics data for Pack formulas.
- List packsGet the list of accessible Packs.
- List page analyticsReturns page-level analytics data for pages within a document. Shows metrics like views and sessions per page over time. **Important:** This endpoint requires the document to be in an Enterprise works
- List Page ContentTool to list page content. Returns the content of the specified page. Use when you need to retrieve the content elements from a Coda page.
- 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 or data analysis too
- List tablesReturns a list of tables in a Coda doc.
- 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 User Pack InvitationsTool to get pending Pack invitations for the authenticated user. Use when you need to retrieve invitations to collaborate on Packs.
- List workspace rolesReturns a list of the counts of users over time by role for the workspace. Note: This endpoint requires a workspace that belongs to an organization (Enterprise feature). Workspaces not belonging to an
- 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. Note: This endpoint requires a workspace that belongs to an organiz
- Retrieve the grouped logs of a packRetrieve grouped execution logs for a Pack in a specific Coda document. This endpoint returns Pack invocation logs grouped by execution, showing timestamps, status (success/failed), and detailed log e
- Retrieve the logs of a packRetrieve the execution logs of a Pack within a specific document for debugging purposes. Note: Logs are typically retained for approximately 2 weeks.
- 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 a Pack. This endpoint returns metadata about a Pack's system-level authentication configuration, where the Pack maker's credentials are used for all users. N
- Search principalsSearch for users and groups (principals) that a Coda document can be shared with. This action searches across the workspace for principals matching the query term. The search is case-insensitive and m
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 49 actions.
- 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.
- Insert/Update Rows in Coda TableThis tool allows you to insert new rows into a Coda table or update existing ones based on specified key columns. This is particularly useful for synchronizing data or ensuring records are up-to-date
- Add a category for packAdd a publishing category for a given pack.
- Add a maker for packAdd a maker to a Pack. Makers are users who are displayed as contributors on the Pack's public listing page. You must be an owner or admin of the Pack to add makers. This is typically used to credit c
- Add a permission for packCreate or modify permissions for a given Pack. This action allows you to grant access to a Pack for users or workspaces. If a permission already exists for the specified principal, it will be updated
- Add custom domainAdd a custom domain to a published doc. This action allows you to map a custom domain (like 'docs.yourcompany.com') to a published Coda doc. Before using this action: 1. The doc must be published (use
- Add permissionAdds a new permission to the doc.
- 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 FolderCreates a new folder in a Coda workspace. Use this action to organize documents by creating folders within a workspace. Folders help structure content and make it easier to navigate and manage documen
- Create PackCreates a new Pack in Coda. A Pack is a container for custom functionality that extends Coda's capabilities. This endpoint registers a new Pack and returns its ID. After creation, you'll need to separ
Show all 49
- Create Pack InvitationCreate an invitation for a user to access a Pack. This action sends an invitation to the specified email address, granting them access to the Pack at the specified access level. The invitee will recei
- Delete a category for packDelete a publishing category for a given pack.
- Delete a maker for packRemoves a maker from a Pack's maker list. The maker will no longer be displayed as a contributor on the Pack's public page. This action requires admin access to the Pack. The operation returns success
- Delete a pageDeletes the specified page.
- Delete a permission for packDelete user, workspace, or global permissions for a given Pack.
- Delete docPermanently deletes a Coda doc. This action permanently removes the specified doc and all its contents including pages, tables, formulas, and data. The deletion is processed asynchronously and returns
- Delete FolderTool to delete a folder in Coda. Use when you need to permanently remove a folder. This operation deletes the specified folder.
- Delete multiple rowsDeletes multiple rows from a Coda table or view. This action queues the specified rows for deletion and returns immediately with a 202 status. The actual deletion is processed asynchronously and typic
- Delete packDelete a given Pack.
- Delete Pack listing draftDelete the listing draft for a Pack, discarding any unsaved changes. Tool to delete the listing draft for a Pack, discarding any unsaved changes. Use when you need to discard a draft listing for a Pac
- Delete Page ContentTool to delete content from a Coda page. Use when you need to remove specific elements or all content from a page. This endpoint returns a 202 status code indicating the deletion has been queued and w
- Delete permissionDeletes an existing permission from a Coda document. This action permanently removes access for a specific user, group, or domain that was previously granted to the document. To use this action, you m
- 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 deletions are generall
- Deletes a custom domainDeletes a custom domain from a published doc.
- Pack asset upload completeNotify Coda that the Pack asset upload to S3 is complete. This action is the final step in the Pack asset upload workflow: 1. Call upload_a_pack_asset to get a signed S3 URL and packAssetUploadedPathN
- Pack source code upload completeNotify Coda that the Pack source code upload to S3 is complete. This action is the final step in the Pack source code upload workflow: 1. Call upload_pack_source_code to get a signed S3 URL 2. Upload
- Pack version upload completeMark a Pack version upload as complete to finalize the Pack version creation. This action is part of a multi-step workflow for creating Pack versions: 1. First, register a new Pack version using the '
- 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 perform any action on the
- Register pack versionRegisters a new Pack version and obtains a signed upload URL. This is the first step in the Pack version upload workflow. It registers a new version with Coda and returns a pre-signed S3 URL along wit
- 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 a 404 if the resour
- Set the oauth configurations of the packSet OAuth2 client credentials (client ID, secret, redirect URI) for a Pack. Prerequisites: The Pack must have OAuth2 authentication defined in its source code using setUserAuthentication() with author
- Set the system connection credentials of the packSet the system connection credentials of the Pack. This endpoint completely replaces the existing system connection credentials for a Pack. System connection credentials are used when a Pack is config
- Trigger automationTriggers a webhook-invoked automation in a Coda doc. This action triggers an automation that has been configured with "Webhook invoked" as its trigger type. When triggered, the automation will execute
- Unpublish docUnpublishes a Coda document, removing it from public access. This action removes the document from the Coda Gallery and makes it private to the workspace. The operation succeeds even if the document i
- Update acl settingsUpdate access control list (ACL) settings for a Coda document. This action allows you to control sharing and permission settings: - Whether editors can manage document permissions - Whether viewers ca
- Update an existing Pack releaseUpdate the release notes of an existing Pack release. Use this to modify the description and changelog information displayed to users who have installed or are considering installing your Pack.
- 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 docUpdates metadata for a Coda document, including its title and icon. This action allows you to modify: - Document title/name - Document icon Note: Updating a doc title requires you to be a Doc Maker in
- Update featured docs for a packCreate or replace the featured docs for a Pack. Featured docs are example or template documents that showcase how to use the Pack. This action replaces the entire list of featured docs (it does not ap
- Update FolderTool to update folder metadata in Coda. Use when you need to modify the name or description of an existing folder. Note that some folder types (like personal folders) cannot be edited.
- 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. **Requirements:** - The workspace must belong to an
- 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.
Changes wait in Needs you
Changes and sends in Coda are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Coda questions
Can an agent change data in Coda on its own?
Not by default. Changes and sends in Coda are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Coda?
This connector lists 56 read actions. Reads run at once, without waiting for approval.
How does Coda connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.