Collaborative workspace platform that transforms documents into powerful tools for team productivity and project management
Collaborative workspace platform that transforms documents into powerful tools for team productivity and project management On Nagent, Coda is exposed as a fully-configurable productivity integration that any agent can call — 110 actions, 4 triggers, and API key authentication. No code is required to wire Coda into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Coda to automate the kinds of tasks productivity teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Coda also supports 4 event triggers ("Coda Document Deleted Trigger", "New Coda Document Trigger", "New Coda Page Trigger", and more), which lets your Nagent agents react to Coda activity in real time — for example, kicking off a downstream workflow the moment a relevant event fires.
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Coda into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Triggers are the entry points of agents built on Nagent — pick one to fire your agent the moment a Coda event happens. Webhook triggers run instantly; poll triggers check on an interval you configure. Each shows its configuration parameters and the payload your agent receives.
CODA_DOCUMENT_DELETEDTriggers when a Coda document is deleted.
Configuration
Show only docs belonging to the given folder.
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Show only docs owned by the user.
Show only published docs.
If true, returns docs that are starred. If false, returns docs that are not starred.
Maximum number of items to retrieve in a single poll (1-100).
Show only docs belonging to the given workspace.
Payload
The document that was deleted
Type of event
CODA_NEW_CODA_DOCUMENTTriggers when a new Coda document is created.
Configuration
Show only docs belonging to the given folder.
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Show only docs owned by the user.
Show only published docs.
If true, returns docs that are starred. If false, returns docs that are not starred.
Maximum number of items to retrieve in a single poll (1-100).
Show only docs belonging to the given workspace.
Payload
The browser link to the document
The creation timestamp of the document
The ID of the folder containing the document
The URL of the document
The ID of the document
The name of the document
The email of the document owner
The name of the document owner
The type of the document
The last update timestamp of the document
The ID of the workspace containing the document
CODA_NEW_CODA_PAGETriggers when a new page is added to a Coda document.
Configuration
ID of the Coda document to monitor for new pages.
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Maximum number of pages to retrieve in a single poll (1-100).
Payload
Type of event
The page that triggered the event
CODA_SPECIFIC_CODA_PAGE_UPDATEDTriggers when a specific page within a Coda document is updated.
Configuration
ID of the Coda document containing the page to monitor.
Periodic Interval to Check for Updates & Send a Trigger in Minutes
ID or name of the specific page to monitor for updates.
Payload
Type of event
The page that was updated
Every operation an agent can call against Coda, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CODA_ADD_A_CATEGORY_FOR_PACKAdd a publishing category for a given pack.
Input parameters
ID of a Pack
Name of the publishing category.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 collaborators and team members who contributed to the Pack's development.
Input parameters
The unique identifier of the Pack. You must have admin/owner permissions on this Pack to add makers.
The email address (login ID) of the user to add as a Pack maker. This user will be displayed as a maker on the Pack's public listing page.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 with the new access level. The API returns a permission ID which is the same for updates to existing permissions. Note: You must have admin access to the Pack to manage its permissions.
Input parameters
Access level to grant for the Pack. Options: - 'view': Can view the Pack and its details. - 'test': Can test the Pack in their docs. - 'edit': Can modify the Pack (requires maker permissions). - 'admin': Full administrative access to the Pack.
ID of a Pack
Metadata about a Pack principal. Must be a dictionary specifying who gets the permission. Supported types: 1) Workspace: {"type": "workspace", "workspaceId": "ws-xxx"} - Grant permission to an entire workspace. 2) User (email): {"type": "email", "email": "user@example.com"} - Grant permission to a specific user by email. Note: Not all principal types may be supported depending on pack configuration and user permissions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 CODA_PUBLISH_DOC action first) 2. Your Coda account must have a paid plan (Pro, Team, or Enterprise) 3. You'll need to configure DNS settings at your domain registrar after adding the domain The domain setup typically takes 5-10 minutes to initialize after DNS is configured. You can check the status using CODA_LIST_CUSTOM_DOC_DOMAINS action. Note: Custom domains are NOT available on Coda's Free tier.
Input parameters
The unique identifier of the Coda doc to which the custom domain will be added. The doc must be published before adding a custom domain. Example: 'dG7v27oLhI'
The custom domain name to add to the published doc (e.g., 'docs.example.com' or 'www.mysite.com'). You must configure DNS settings at your domain registrar to point to Coda's servers before the domain will be fully functional.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_ADD_PERMISSIONAdds a new permission to the doc.
Input parameters
ID of the doc.
Type of access to grant. 'readonly' allows viewing only, 'write' allows editing, 'comment' allows commenting.
The user, group, domain, or anyone principal to grant access to. Use type='email' with email field for individual users, type='group' with groupId for groups, type='domain' with name for domain access, or type='anyone' for public access.
When true, suppresses email notification to the principal about the new permission. Default is false.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 asynchronously. Use the returned 'href' URL with the 'content_export_status' action to poll for completion and retrieve the exported content.
Input parameters
Unique identifier of the Coda document containing the page to export.
Output format for the exported page content. Supported formats are 'html' (preserves rich formatting) and 'markdown' (provides plain text representation).
ID or name of the page to export. Page IDs are recommended (format: 'canvas-XXXXXXXX') as they are stable. Names can be used but should be URI-encoded and may be ambiguous if multiple pages share the same name. When multiple pages have the same name, an arbitrary one will be selected.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
The unique identifier of the Coda document containing the page.
The unique identifier of the content export request, obtained from the 'Begin content export' action.
ID or name of the page. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it. If you provide a name and there are multiple pages with the same name, an arbitrary one will be selected.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_COPY_DOCCreates 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.
Input parameters
Title for the new document. If not specified, defaults to 'Untitled'.
The timezone to use for the newly created document.
The ID of the folder where the new document will be created. If not specified, defaults to your 'My docs' folder.
ID of the existing document to copy.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_CREATE_A_NEW_PACK_RELEASECreates a new Pack release based on an existing Pack version.
Input parameters
ID of a Pack
The semantic version of the Pack to release (e.g., '1.0.0', '1.2.3'). Must be an existing Pack version.
Optional release notes describing changes, improvements, or fixes in this release.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
Name of the page.
ID of the doc.
Name of the icon.
Url of the cover image to use.
Subtitle of the page.
Content for the page. Must be a discriminated union with a 'type' field. Valid types: 'canvas' for text/rich text content, 'embed' for full-page embeds. For canvas: {'type': 'canvas', 'canvasContent': {'format': 'html'\\ | 'markdown', 'content': '...'}}. For embed: {'type': 'embed', 'url': 'https://...'}. NOTE: Tables cannot be created via pageContent - use separate table insertion APIs after page creation.
The ID of this new page"s parent, if creating a subpage.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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).
Input parameters
Title of the new doc. Defaults to "Untitled".
The ID of the folder within which to create this doc. Defaults to your "My docs" folder in the oldest workspace you joined; this is subject to change. You can get this ID by opening the folder in the docs list on your computer and grabbing the `folderId` query parameter.
The timezone to use for the newly created doc.
An optional doc ID from which to create a copy.
The initial page to create in the doc. Can include properties like 'name' (page title), 'subtitle', 'iconName', 'imageUrl', 'parentPageId', and 'pageContent' (with 'type': 'canvas' and 'canvasContent' containing HTML). This allows you to pre-configure the first page of the newly created document.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 documents.
Input parameters
Name of the folder to create.
Description of the folder to provide context about its purpose.
ID of the workspace where the folder should be created.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 separately upload the Pack's source code and assets. Prerequisites: - You must have appropriate permissions in the target workspace - The workspace must allow Pack creation Next steps after creation: 1. Upload Pack source code using the upload pack source code endpoint 2. Upload Pack assets (logos, images) using the upload pack asset endpoint 3. Register a Pack version to make it available for use
Input parameters
The name for the Pack. This is a required field and will be displayed to users when they browse or search for Packs. Should be descriptive and unique within your workspace. Can be an empty string but it's recommended to provide a meaningful name.
A brief description of what the Pack does and its purpose. This helps users understand the Pack's functionality. Optional but recommended for better discoverability. Can include details about features, use cases, or any special requirements.
The parent workspace ID where the Pack will be created. If not specified, the Pack will be created in the authenticated user's default workspace. You can obtain workspace IDs from the user info or list docs endpoints.
The ID of an existing Pack to fork/copy from. Use this when creating a new Pack based on an existing one. The new Pack will inherit the source Pack's code and configuration. Leave empty for creating a Pack from scratch.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 receive an email notification with instructions to accept the invitation. Prerequisites: - You must have appropriate permissions (admin or owner) on the Pack to create invitations - The email address must be valid Note: The invitation must be accepted by the recipient to grant them actual access to the Pack.
Input parameters
Email address of the user to invite to the Pack. The invitation will be sent to this email address.
Access level to grant for the Pack. Options: 'none' - No access, 'view' - Can view the Pack and its details, 'test' - Can test the Pack in their docs, 'edit' - Can modify the Pack (requires maker permissions), 'admin' - Full administrative access to the Pack.
ID of the Pack to create an invitation for. You must have appropriate permissions on this Pack to create invitations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_DELETE_A_CATEGORY_FOR_PACKDelete a publishing category for a given pack.
Input parameters
ID of a Pack
Name of a publishing category
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 successfully even if the maker was not previously listed for the Pack.
Input parameters
The unique numeric identifier of the Pack from which to remove the maker.
The email address of the maker to be removed from the Pack's maker list.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_DELETE_A_PAGEDeletes the specified page.
Input parameters
ID of the doc.
ID or name of the page. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it. If you provide a name and there are multiple pages with the same name, an arbitrary one will be selected.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_DELETE_A_PERMISSION_FOR_PACKDelete user, workspace, or global permissions for a given Pack.
Input parameters
ID of a Pack
ID of a permission on a pack.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 immediately with a 202 Accepted status. The doc will be fully deleted within a few seconds. **Warning**: This is a destructive operation that cannot be undone. Ensure you have the correct doc ID before executing this action. **Permissions**: You must be the owner of the doc or have appropriate deletion permissions. **Error Responses**: - 404: The doc does not exist or you don't have access to it - 401: Invalid or expired API token - 403: You don't have permission to delete this doc
Input parameters
The unique identifier of the doc to delete. This is the alphanumeric ID found in the doc's URL (e.g., 'AbCDeFGH' from https://coda.io/d/_dAbCDeFGH).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_DELETE_FOLDERTool to delete a folder in Coda. Use when you need to permanently remove a folder. This operation deletes the specified folder.
Input parameters
ID of the folder to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 typically completes within several seconds. Use the returned requestId with the getMutationStatus endpoint to verify completion if needed.
Input parameters
ID of the Coda document containing the table with rows to delete.
Array of row IDs to delete from the table. Each ID should be in the format 'i-xxxxxxxxxx'.
ID or name of the table containing the rows to delete. Table IDs (e.g., 'grid-abc123') are recommended over names since names can be changed by users.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_DELETE_PACKDelete a given Pack.
Input parameters
ID of a Pack
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 Pack without publishing it. This removes the draft version and reverts to the last published listing (if any). **Important**: This action permanently discards all unpublished changes to the Pack listing. To publish changes instead of discarding them, use the appropriate publish action.
Input parameters
ID of the Pack whose listing draft should be deleted. This is the unique numeric identifier assigned when the Pack was created.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 will be processed within seconds.
Input parameters
ID of the doc containing the page.
IDs of the elements to delete from the page. If omitted or empty, all content will be deleted.
ID or name of the page. Names are discouraged because they're easily prone to being changed by users. If you provide a name and there are multiple pages with the same name, an arbitrary one will be selected. Note: URI encoding is handled automatically.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 must first obtain the permissionId from the LIST_PERMISSIONS action. The deletion is immediate and cannot be undone through the API. Common use cases: - Revoking access when a user no longer needs to view/edit the document - Managing document security by removing obsolete permissions - Cleaning up permissions after organizational changes Note: This action requires appropriate permissions to manage document access.
Input parameters
The unique identifier of the Coda document from which to delete the permission. Can be obtained from LIST_AVAILABLE_DOCS or CREATE_DOC actions.
The unique identifier of the permission to delete. This ID can be retrieved from the LIST_PERMISSIONS action. Each permission represents access granted to a specific user, group, or domain for the document.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 generally processed within several seconds. When deleting using a name as opposed to an ID, an arbitrary row will be removed.
Input parameters
ID of the doc.
ID or name of the row. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it. If there are multiple rows with the same value in the identifying column, an arbitrary one will be selected.
ID or name of the table. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_DELETES_A_CUSTOM_DOMAINDeletes a custom domain from a published doc.
Input parameters
ID of the Coda doc from which to remove the custom domain. Example: 'rqC5QoVKYT'
The custom domain name to delete (e.g., 'example.com', 'docs.mycompany.io'). Note: The API returns 200 OK even if the domain doesn't exist on the doc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_FETCH_GROUPED_LOGS_BY_PACK_ORG_ROOT_INGESTION_IDRetrieve the grouped logs of a Pack ingestion for debugging purposes. This action is used with Coda Brain (Enterprise feature) to retrieve and debug logs from Pack ingestion processes. It provides detailed log information grouped by invocation, including timestamps, log levels, messages, and execution status. Note: This endpoint requires valid organizationId and rootIngestionId values which are only available for Enterprise accounts with Coda Brain enabled. These IDs track data ingestion from external sources via Packs.
Input parameters
A search query that follows Lucene syntax.
Maximum number of results to return in this query.
Specifies if the logs will be returned in time desc or asc. Default is desc.
ID of a Pack
An opaque token used to fetch the next page of results.
Only return logs after the given time (non-inclusive).
ID of the organization.
Only return logs before the given time (non-inclusive).
ID of the root ingestion.
ID of the ingestion execution.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_FETCH_INGESTION_EXECUTIONS_FOR_PACKRetrieve the ingestion execution ids of a root ingestion for debugging purpose. This action is typically used with Coda Brain (Enterprise feature) to track and debug data ingestion processes from external sources via Packs. Note: This endpoint requires valid organizationId and rootIngestionId values which are only available for Enterprise accounts with Coda Brain enabled.
Input parameters
Maximum number of results to return in this query.
Sort order for ingestion executions by time: 'asc' (ascending/oldest first) or 'desc' (descending/newest first). Default is 'desc'.
ID of a Pack
An opaque token used to fetch the next page of results.
Filter results by datasource name (e.g., the external data source being ingested).
Filter results by execution type: 'FULL' (complete data sync) or 'INCREMENTAL' (delta/changes only).
Only return ingestion executions after the given time (non-inclusive). Format: ISO 8601 timestamp.
Filter results by specific CSB (Coda Sync Bridge) ingestion ID.
ID of the organization. This is an Enterprise-level identifier used with Coda Brain features.
Only return ingestion executions before the given time (non-inclusive). Format: ISO 8601 timestamp.
Filter results by ingestion execution status. Options: QUEUED, STARTED, CANCELLED, UP_FOR_RETRY, COMPLETED, FAILED.
ID of the root ingestion. This identifies a specific data ingestion process in Coda Brain.
Filter results by specific CSB (Coda Sync Bridge) ingestion execution ID.
Include deleted ingestion executions in the response. Default is false.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_ACL_SETTINGSReturns settings associated with ACLs for this Coda doc.
Input parameters
ID of the doc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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, etc.) - Whether it's a display column or calculated column - Formula (for calculated columns) - Default value - Parent table and page information
Input parameters
ID of the Coda document.
ID or name of the table. Names are discouraged because they're easily prone to being changed by users. If you're using a name, be sure to URI-encode it.
ID or name of the column. Names are discouraged because they're easily prone to being changed by users. If you're using a name, be sure to URI-encode it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_A_CONTROLReturns info on a control.
Input parameters
ID of the doc.
ID or name of the control. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_A_FORMULAReturns info on a formula.
Input parameters
ID of the doc.
ID or name of the formula. Names are discouraged because they're easily prone to being changed by users. If you're using a name, be sure to URI-encode it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_ANALYTICS_LAST_UPDATED_DAYReturns days based on Pacific Standard Time when analytics were last updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_A_PAGEReturns details about a page.
Input parameters
ID of the doc.
ID or name of the page. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it. If you provide a name and there are multiple pages with the same name, an arbitrary one will be selected.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 read data from a specific row in a Coda document.
Input parameters
Unique identifier of the Coda document containing the table and row.
ID or name of the row to retrieve. Row IDs (e.g., 'i-xyz123') are recommended over names as names can be changed by users. If using a name, ensure it is properly URI-encoded. If multiple rows have the same name value, an arbitrary one will be returned.
Format for cell values in the response. Options: 'simple' (default) returns primitive types (string/number/boolean) with arrays as comma-delimited strings; 'simpleWithArrays' returns arrays as JSON arrays; 'rich' returns values with full encoding including Markdown for text and structured data for complex types (currency, person, image, etc.).
ID or name of the table containing the row. Table IDs (e.g., 'grid-xyz123') are recommended over names as names can be changed by users. If using a name, ensure it is properly URI-encoded.
When true, returns column names as keys in the values object instead of column IDs. Default is false. Using column IDs is recommended as column names can be changed by users, which may break integrations relying on specific names.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_A_SINGLE_PACKRetrieves 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 accessible for Packs that the authenticated user has created or has been granted access to.
Input parameters
The unique identifier of the Pack to retrieve. Must be a Pack that the authenticated user has created or has access to. You can obtain Pack IDs by creating a new Pack with the 'create_pack' action or by listing accessible Packs with the 'list_packs' action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_A_TABLEReturns details about a specific table or view.
Input parameters
ID of the doc.
ID or name of the table. Names are discouraged because they're easily prone to being changed by users. If you're using a name, be sure to URI-encode it.
Return "detail" and "form" for the `layout` field of detail and form layouts respectively (instead of "masterDetail" for both)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 permissions. This endpoint provides the same information displayed on the Pack's public listing page in the Coda Pack gallery. Optionally accepts workspace/document context to check installation privileges and release channel to retrieve specific versions (LIVE or LATEST).
Input parameters
Optional document ID to check installation privileges for that specific document. If provided, the response will include user access permissions relative to this document.
ID of the Pack to retrieve detailed listing information for.
Optional workspace ID to check installation privileges in that specific workspace. If provided, the response will include user access permissions relative to this workspace.
Optional installation context type (workspace or doc) to specify where the Pack would be installed. When provided, must be accompanied by the corresponding workspaceId (if context is 'workspace') or docId (if context is 'doc'). Affects the userAccess permissions returned in the response.
Optional release channel to retrieve Pack information for. LIVE returns the current live/production version, LATEST returns the most recently uploaded version (may be unpublished).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
Limit results to activity on or after this date. Format: YYYY-MM-DD (e.g., '2025-01-01').
Limit results to activity on or before this date. Format: YYYY-MM-DD (e.g., '2025-12-31').
Limit results to only published items.
ID of the workspace to filter analytics. If not specified, returns analytics for all accessible workspaces.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
ID of the folder.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 location, size metrics (page count, row count, table count), icon, publication status, and source document reference if the doc was copied from another. This is useful for understanding document properties, discovering document structure, and tracking document relationships.
Input parameters
The unique identifier of the Coda document. This is the document ID visible in the URL (e.g., 'abc123XYZ' from 'https://coda.io/d/_dabc123XYZ').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 a 202 status with a requestId. These operations are queued and processed asynchronously (usually within a few seconds). Use this tool to verify that your mutation has been successfully applied before proceeding with dependent operations. Important notes: - Mutation status information is only available for about 24 hours after completion - This should be used shortly after the mutation request was made - Returns completed=true when the operation has finished, completed=false if still pending
Input parameters
The unique request identifier returned from a mutation operation (e.g., 'mutate:c39bd6d9-2719-40e4-bd21-110f3c520031'). This ID is provided in the response from mutation endpoints like upsert rows, delete row, or push button.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 installations - Total workspace installations All query parameters are optional. If no filters are specified, returns analytics for all Packs the authenticated user can edit.
Input parameters
Which Pack IDs to fetch. Note: This parameter may not be supported by the API endpoint.
Limit results to activity on or after this date (ISO 8601 format, e.g., '2024-01-01').
Limit results to activity on or before this date (ISO 8601 format, e.g., '2024-12-31').
Limit results to only published Packs. If false or unspecified, returns analytics for all Packs including published ones.
ID of the workspace to filter analytics by.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 where to configure DNS settings when setting up custom domains for published Coda docs.
Input parameters
The domain name to check (e.g., 'example.com' or 'docs.example.com'). Can be any valid domain; does not need to be configured in Coda.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_SHARING_METADATAReturns metadata associated with sharing for this Coda doc.
Input parameters
ID of the doc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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, endpoint configurations, sharing permissions, and which Pack components (formulas, actions, sync tables) are available for use.
Input parameters
The unique numeric ID of the Coda Pack for which to retrieve the configuration schema. This ID can be obtained from the List Packs endpoint.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 versions must exist for the specified pack.
Input parameters
ID of a Pack. Must be a pack you own or have access to.
Semantic version of the previous/base Pack version (e.g., '1.0.0'). This version must exist for the specified pack.
Semantic version of the new/target Pack version to compare against (e.g., '1.1.0'). This version must exist for the specified pack.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 returns validation findings if there are any issues with the metadata. This is typically used before registering and uploading a new Pack version. Note: This endpoint only works with Packs that the authenticated user owns or has appropriate permissions to manage.
Input parameters
ID of a Pack
The SDK version the metadata was built on.
The metadata for the next version of the Pack as a JSON string. This typically includes Pack definition metadata such as formulas, sync tables, authentication configuration, and other Pack features. The API will validate this metadata and return the next valid version number along with any validation findings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 reviewing, auditing, backing up, or comparing Pack code between versions. Prerequisites: - Pack must exist and be accessible to the authenticated user - Version must have been created with source code uploaded - Use CODA_LIST_PACKS to find Pack IDs and CODA_LIST_THE_VERSIONS_FOR_A_PACK for versions Important: URLs expire within hours, so download files promptly. Returns empty array if no source code was uploaded for the version. This action only returns URLs, not file contents.
Input parameters
ID of the Pack to retrieve source code from. You can obtain Pack IDs by using CODA_LIST_PACKS or CODA_CREATE_PACK actions. The Pack must be accessible to the authenticated user (owner, collaborator, or viewer with appropriate permissions).
Semantic version number of the Pack version to retrieve source code for. Must follow semantic versioning format (e.g., '1.0.0', '2.3.5', '0.1.0'). Use CODA_LIST_THE_VERSIONS_FOR_A_PACK to get available versions for a Pack. Note that source code is only available for versions where it was explicitly uploaded during the Pack version creation process.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_GET_USER_INFOReturns basic info about the current user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 relevant to the user (last viewed, edited, or shared).
Input parameters
Maximum number of results to return in this query.
Search term used to filter down results.
Show only docs owned by the user.
Show only docs belonging to the given folder.
Show only docs visible within the gallery.
If true, returns docs that are starred. If false, returns docs that are not starred.
An opaque token used to fetch the next page of results.
Show only docs copied from the specified doc ID.
Show only published docs.
Show only docs belonging to the given workspace.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
The numeric ID of the Coda Pack to retrieve categories for. You can obtain pack IDs from the list_packs action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_COLUMNSReturns a list of columns in a table.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
An opaque token used to fetch the next page of results.
If true, returns only visible columns for the table. This parameter only applies to base tables, and not views.
ID or name of the table. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_CONTROLSReturns a list of controls in a Coda doc.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
Determines how to sort the given objects.
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 empty list if no custom domains are configured.
Input parameters
ID of the doc. This is the unique identifier for the Coda document (e.g., 'DUTh3qjMrM'). You can get this from creating a doc or listing available docs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 range, publication status, and search query. Results can be aggregated daily or cumulatively and sorted by various document properties or metric values.
Input parameters
Maximum number of results to return in this query.
Search term to filter documents by name or title. Returns only documents matching this query string.
Time period granularity for metrics aggregation. 'daily' returns metrics per day (default), 'cumulative' returns aggregated metrics over the entire date range.
List of document IDs to filter analytics. Provide as an array of doc IDs (e.g., \['docId1', 'docId2'\]). If not specified, returns analytics for all accessible documents.
Field to sort results by. Options include document properties (date, docId, title, createdAt, publishedAt) or metric values (likes, copies, views, sessions, aiCredits).
Sort direction. 'ascending' for lowest to highest, 'descending' for highest to lowest. Use with orderBy parameter.
Pagination token for fetching subsequent pages. Use the 'nextPageToken' value from a previous response to retrieve the next set of results.
Start date for analytics data range in ISO 8601 format (YYYY-MM-DD). Returns metrics on or after this date. Example: '2025-01-01'.
End date for analytics data range in ISO 8601 format (YYYY-MM-DD). Returns metrics on or before this date. Example: '2025-12-31'.
Filter by publication status. Set to true to return only published documents, false for unpublished, or omit to include all.
Filter analytics to documents in a specific workspace. Provide the workspace ID (e.g., 'ws-1234Abcd').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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), whether it's pinned at the top, and its published URL if available.
Input parameters
The unique numeric identifier of the Pack whose featured docs you want to retrieve. You can get pack IDs from the list_packs action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 folder by workspace.
Input parameters
Maximum number of results to return in this query. Default is 25.
If true, returns folders that are starred. If false, returns folders that are not starred. If not specified, returns all folders.
An opaque token used to fetch the next page of results.
Show only folders belonging to the given workspace.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_FORMULASReturns a list of named formulas in a Coda doc.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
Determines how to sort the given objects.
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_MAKERS_FOR_PACKList makers for a given pack.
Input parameters
ID of a Pack
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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, invocation metrics, and active usage statistics. All parameters are optional - if no filters are specified, returns analytics for all accessible Packs. Common use cases: - Get analytics for all accessible packs (no parameters) - Filter by workspace using workspaceId - Filter by date range using sinceDate/untilDate - Sort results using orderBy and direction - Paginate through results using limit and pageToken
Input parameters
Maximum number of results to return per page. Defaults to 1000. Use with pageToken for pagination.
Search term used to filter pack analytics by pack name or other attributes.
Quantization period over which to view analytics. Options: 'daily' (default) for daily metrics, or 'cumulative' for cumulative totals.
Field to sort the pack analytics by. Options include: 'date', 'packId', 'name', 'createdAt', 'docInstalls', 'workspaceInstalls', 'numFormulaInvocations', 'numActionInvocations', 'numSyncInvocations', and various activelyUsing metrics.
Which Pack IDs to fetch. Note: This parameter may not be supported by the Coda API and may result in a 400 error if used.
Direction to sort results in. Options: 'ascending' or 'descending'. Use with orderBy parameter.
An opaque token used to fetch the next page of results. Obtain this from the 'nextPageToken' field in a previous response.
Limit results to activity on or after this date (ISO 8601 format, e.g., '2024-01-01').
Limit results to activity on or before this date (ISO 8601 format, e.g., '2024-12-31').
Limit results to only published packs. Set to true to get only published packs, or false/unspecified to get all packs including published ones.
ID of the workspace to filter pack analytics by. Use this to get analytics only for packs in a specific workspace.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_PACK_FORMULA_ANALYTICSReturns analytics data for Pack formulas.
Input parameters
Maximum number of results to return in this query.
Quantization period over which to view analytics. Defaults to daily.
ID of the Pack for which to retrieve formula analytics. You must have edit access to the pack.
Field by which to sort the analytics results. Options include date, formulaName, formulaInvocations, medianLatencyMs, errors, docsActivelyUsing, and various time-based active usage metrics.
Direction to sort results in. Use 'ascending' for lowest to highest, 'descending' for highest to lowest.
An opaque token used to fetch the next page of results.
Limit results to activity on or after this date. Use ISO 8601 date format (e.g., '2024-01-15').
Limit results to activity on or before this date. Use ISO 8601 date format (e.g., '2024-12-31').
A list of Pack formula names (case-sensitive) for which to retrieve analytics. If not specified, returns analytics for all formulas in the pack.
A list of Pack formula types corresponding to the `packFormulaNames`. If specified, this must have the same length as `packFormulaNames`.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_PACKSGet the list of accessible Packs.
Input parameters
Maximum number of results to return in this query.
The sort order of the Packs returned.
Direction to sort results in.
An opaque token used to fetch the next page of results.
Deprecated, use accessTypes instead. Filter to only return the Packs for which the current user has this access type
Filter to only return the Packs for which the current user has these access types.
Use only this workspace (not all of a user"s workspaces) to check for Packs shared via workspace ACL.
Only get Packs shared with users/workspaces, not publicly.
Filter to only Packs whose parent workspace is one of the given IDs.
Do not include Packs that are only shared with workspaces.
Do not include Packs that are only shared with the user individually.
Include Packs that only support Coda Brain.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 workspace. If the document is not in an Enterprise workspace, the API will return a 401 Unauthorized error with the message: "Page level analytics are only available for Enterprise and higher plans".
Input parameters
ID of the doc. Must be a doc in an Enterprise workspace.
Maximum number of results to return in this query.
An opaque token used to fetch the next page of results.
Limit results to activity on or after this date (ISO 8601 format, e.g., '2024-01-15').
Limit results to activity on or before this date (ISO 8601 format, e.g., '2024-01-31').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
Maximum number of content items to return in this query. Default is 50.
ID of the doc containing the page.
An opaque token used to fetch the next page of results.
Format for content output.
ID or name of the page. Names are discouraged because they're easily prone to being changed by users. If you provide a name and there are multiple pages with the same name, an arbitrary one will be selected. Note: URI encoding is handled automatically.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_PAGESReturns a list of pages in a Coda doc.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_PERMISSIONSReturns a list of permissions for this Coda doc.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_PERMISSIONS_FOR_A_PACKGet user, workspace, and/or global permissions for a given Pack.
Input parameters
ID of a Pack
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 tools. Use this when you need to access the content of a table in your Coda document, such as for reporting, data synchronization, or building custom views of your data outside of Coda. The endpoint supports pagination for large tables and allows you to control the number of rows returned per request. It's important to note that this endpoint only retrieves data and doesn't modify the table contents.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
Query used to filter returned rows, specified as `<column_id_or_name>:<value>`. If you"d like to use a column name instead of an ID, you must quote it (e.g., `"My Column":123`). Also note that `value` is a JSON value; if you"d like to use a string, you must surround it in quotes (e.g., `"groceries"`).
Specifies the sort order of the rows returned. If left unspecified, rows are returned by creation time ascending. "UpdatedAt" sort ordering is the order of rows based upon when they were last updated. This does not include updates to calculated values. "Natural" sort ordering is the order that the rows appear in the table view in the application. This ordering is only meaningfully defined for rows that are visible (unfiltered). Because of this, using this sort order will imply visibleOnly=true, that is, to only return visible rows. If you pass sortBy=natural and visibleOnly=false explicitly, this will result in a Bad Request error as this condition cannot be satisfied.
An opaque token used to fetch the next page of results.
An opaque token returned from a previous call that can be used to return results that are relevant to the query since the call where the syncToken was generated.
The format that cell values are returned as.
If true, returns only visible rows and columns for the table.
ID or name of the table. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it.
Use column names instead of column IDs in the returned output. This is generally discouraged as it is fragile. If columns are renamed, code using original names may throw errors.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_TABLESReturns a list of tables in a Coda doc.
Input parameters
ID of the doc.
Maximum number of results to return in this query.
Determines how to sort the given objects.
An opaque token used to fetch the next page of results.
Comma-separated list of table types to include in results. If omitted, includes both tables and views.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_THE_PACK_LISTINGS_ACCESSIBLE_TO_A_USERGet listings of public Packs and Packs created by you.
Input parameters
Maximum number of results to return in this query.
Specify a sort order for the returned Pack listings returned.
Deprecated: use sortBy instead.
Which Pack IDs to fetch.
Direction to sort results in.
An opaque token used to fetch the next page of results.
Type of installation context for which Pack information is being requested.
Use only this workspace (not all of a user"s workspaces) to check for Packs shared via workspace ACL.
Pack access types.
Only get Packs shared with users/workspaces, not publicly.
Filter to only Packs whose parent workspace is one of the given IDs.
Do not include Packs that are only shared with workspaces.
Do not include Packs that are only shared with the user individually.
Include Packs that only support Coda Brain.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_THE_RELEASES_FOR_A_PACKGet the list of releases of a Pack.
Input parameters
Maximum number of results to return in this query.
ID of a Pack
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_THE_VERSIONS_FOR_A_PACKGet the list of versions of a Pack.
Input parameters
Maximum number of results to return in this query.
ID of a Pack
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_LIST_USER_PACK_INVITATIONSTool to get pending Pack invitations for the authenticated user. Use when you need to retrieve invitations to collaborate on Packs.
Input parameters
Maximum number of results to return in this query. Default is 25.
An opaque token used to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 organization will return a 400 error with message "Workspace does not belong to an organization."
Input parameters
ID of the workspace (must belong to an organization). Use CODA_GET_USER_INFO to get your workspace ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 organization (Enterprise feature). Workspaces not belonging to an organization will return a 400 error with message "Workspace does not belong to an organization."
Input parameters
An opaque token used to fetch the next page of results.
ID of the workspace (must belong to an organization). Use CODA_GET_USER_INFO to get your workspace ID.
Show only the members that match the included roles. Multiple roles can be specified with a comma-delimited list.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 packAssetUploadedPathName 2. Upload your image file (logo/cover/example) directly to the S3 URL using HTTP PUT 3. Call this action to notify Coda that the upload is complete and register the asset The packAssetId must be extracted from the packAssetUploadedPathName returned by upload_a_pack_asset. The packAssetType must match the type specified when initiating the upload. Supported asset types: - logo: Pack logo image (max 5MB, square recommended) - cover: Pack cover image (max 5MB, 1200x630px recommended) - exampleImage: Pack example/screenshot images (max 75MB) After completion, the asset will be processed and available for display in the Pack gallery and listing.
Input parameters
The unique ID of the Pack. This ID is returned when creating a Pack and identifies which Pack the asset belongs to.
The unique identifier for the Pack asset (a long hash string). This is the asset ID from the packAssetUploadedPathName returned by upload_a_pack_asset, extracted from the path: /packs/{packId}/assets/{packAssetId}/assetType/{packAssetType}/uploadComplete
The type of Pack asset being uploaded. Must be one of: 'logo' (Pack logo image), 'cover' (Pack cover image), or 'exampleImage' (Pack example/screenshot image). Must match the asset type specified when initiating the upload with upload_a_pack_asset.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 your source code file to the S3 URL 3. Call this action to notify Coda that the upload is complete The filename and codeHash parameters must match the values used when initiating the upload with upload_pack_source_code.
Input parameters
The unique ID of the Pack. This ID is returned when creating a Pack and identifies which Pack the source code belongs to.
A SHA-256 hash of the source code file contents (64 hex characters). Used to verify file integrity and identify duplicate uploads. Must exactly match the hash provided when initiating the upload with upload_pack_source_code.
The filename of the source code file that was uploaded to S3. Must exactly match the filename provided when initiating the upload with upload_pack_source_code.
The semantic version string for this Pack version (e.g., '1.0.0', '2.1.3-beta'). Must match the version used when initiating the upload with upload_pack_source_code.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 'Register pack version' action, which returns a signed upload URL 2. Upload your Pack version bundle (JavaScript/TypeScript code) to the signed URL 3. Call this action to notify Coda that the upload is complete and trigger Pack version validation and creation After completion, the Pack version will be validated and available for testing or release. Note: This action will fail with a 400 error if no upload was found for the specified Pack and version.
Input parameters
Developer notes describing changes, improvements, or fixes in this Pack version.
ID of a Pack
Source of the Pack version upload. 'web' indicates uploaded via Coda's web interface, 'cli' indicates uploaded via the Coda CLI tool.
Semantic version of a Pack
Set to true to bypass Coda's protection against SDK version regression when multiple makers build versions. Use with caution as downgrading SDK versions may introduce compatibility issues.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_PATCH_THE_SYSTEM_CONNECTION_CREDENTIALS_OF_THE_PACKPatch the system connection credentials of the Pack.
Input parameters
ID of a Pack
Credentials to be patched for the Pack's system connection. Since this is a PATCH operation, only the provided fields will be updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_PUBLISH_DOCUpdate publish settings for a doc.
Input parameters
Which interaction mode the published doc should use.
Slug for the published doc.
ID of the doc.
If true, new users may be required to sign in to view content within this document. You will receive Coda credit for each user who signs up via your doc.
If true, indicates that the doc is discoverable.
The names of categories to apply to the document.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 document, including writing to other tables and performing Pack actions.
Input parameters
ID of the doc.
ID or name of the row. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it. If there are multiple rows with the same value in the identifying column, an arbitrary one will be selected.
ID or name of the table. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it.
ID or name of the column. Names are discouraged because they"re easily prone to being changed by users. If you"re using a name, be sure to URI-encode it.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 with required headers for uploading the Pack bundle file. Workflow: 1. Call this action with packId, packVersion (semantic version), and bundleHash (SHA-256) 2. Use the returned upload_url and headers to upload your Pack bundle JSON via PUT request 3. After upload completes, call pack_version_upload_complete to finalize the registration 4. Optionally create a release to make the version available to users Prerequisites: - A Pack must exist (create one with CODA_CREATE_PACK if needed) - The version number must be greater than any existing version for this Pack - You must have calculated the SHA-256 hash of your Pack bundle file Note: The version must follow semantic versioning (e.g., 1.0.0, 1.2.3, 2.0.0).
Input parameters
ID of the Pack to register a new version for. You can obtain this from creating a Pack (CODA_CREATE_PACK) or listing Packs (CODA_LIST_PACKS).
SHA-256 hash of the Pack bundle file to be uploaded. This is a 64-character hexadecimal string. The hash is used to verify the integrity of the uploaded file. Calculate this using SHA-256 on your Pack definition JSON file. Example: 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'.
Semantic version number for the Pack version being registered. Must follow semantic versioning format (e.g., '1.0.0', '1.2.3', '2.0.0'). Must be greater than any previously registered version for this Pack. Use patch version for bug fixes (e.g., 1.0.1), minor version for backwards-compatible features (e.g., 1.1.0), and major version for breaking changes (e.g., 2.0.0).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 resource cannot be located with the current credentials.
Input parameters
The browser link to try to resolve.
By default, attempting to resolve the Coda URL of a deleted object will result in an error. If this flag is set, the next-available object, all the way up to the doc itself, will be resolved.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 entries for debugging. Logs are sorted by timestamp (newest first by default) and can be filtered by time range or search query. Use this to debug Pack executions, track errors, and monitor Pack performance in a document.
Input parameters
Search query using Lucene syntax to filter logs by content (e.g., 'error', 'level:error', 'message:failed').
ID of the Coda document where the Pack is used. Use CODA_LIST_AVAILABLE_DOCS to find available document IDs.
Maximum number of grouped log invocations to return per page. Default is 25.
Sort order for logs by timestamp: 'asc' (oldest first) or 'desc' (newest first). Default is 'desc'.
Numeric ID of the Pack whose logs you want to retrieve. Use CODA_LIST_PACKS to find available pack IDs.
Opaque pagination token from a previous response's nextPageToken field. Use to fetch the next page of results.
Return only logs after this timestamp (non-inclusive). Format: ISO 8601 (e.g., '2026-01-01T00:00:00.000Z').
Return only logs before this timestamp (non-inclusive). Format: ISO 8601 (e.g., '2026-01-30T12:00:00.000Z').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_RETRIEVE_THE_INFORMATION_FOR_A_SPECIFIC_LOGRetrieve detailed information for a specific log entry from a Pack ingestion. This action retrieves comprehensive log details for Coda Brain (Enterprise feature) ingestion debugging. It provides in-depth information about specific log entries including user context, action details, entity information, event metadata, and execution results. The action is useful for: - Investigating specific ingestion events or errors - Auditing user actions within Pack ingestion processes - Debugging failed or unexpected ingestion behaviors - Understanding the context of specific log entries Note: This endpoint requires valid organizationId, rootIngestionId, and logId values which are only available for Enterprise accounts with Coda Brain enabled. For non-existent or invalid IDs, the action returns a response with found=False.
Input parameters
The unique identifier of the specific log entry to retrieve.
ID of a Pack
The key identifying which specific details to retrieve from the log entry. This parameter specifies the type of detailed information requested.
ID of the organization. This is an Enterprise-level identifier used with Coda Brain features.
ID of the root ingestion. This identifies a specific data ingestion process in Coda Brain.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_RETRIEVE_THE_LOGS_OF_A_INGESTIONRetrieve the logs of a Ingestion for debugging purpose. This action is typically used with Coda Brain (Enterprise feature) to track and debug data ingestion processes from external sources via Packs. Note: This endpoint requires valid organizationId and rootIngestionId values which are only available for Enterprise accounts with Coda Brain enabled. For non-existent or invalid IDs, the action returns an empty result.
Input parameters
Search query to filter logs. Follows Lucene syntax for complex queries (e.g., 'error AND status:failed').
Maximum number of results to return in this query.
Sort order for logs by timestamp: 'asc' (ascending/oldest first) or 'desc' (descending/newest first). Default is 'desc'.
ID of a Pack
Only return logs of the given types.
An opaque token used to fetch the next page of results.
Only return logs matching provided request IDs.
Only return logs after the given time (non-inclusive). Format: ISO 8601 timestamp.
ID of the organization. This is an Enterprise-level identifier used with Coda Brain features.
Only return logs before the given time (non-inclusive). Format: ISO 8601 timestamp.
ID of the root ingestion. This identifies a specific data ingestion process in Coda Brain.
ID of the ingestion execution.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
A search query that follows Lucene syntax to filter log messages. Example: 'error' or 'status:failed'.
ID of the Coda document where the Pack is installed and being used.
Maximum number of results to return in this query.
Specifies if the logs will be returned in time desc (newest first) or asc (oldest first). Default is desc.
Numeric ID of the Pack whose logs you want to retrieve.
Only return logs of the given types.
An opaque token used to fetch the next page of results.
Only return logs matching provided request IDs.
Only return logs after the given time (non-inclusive). Format: ISO 8601 timestamp.
Only return logs before the given time (non-inclusive). Format: ISO 8601 timestamp.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_RETRIEVE_THE_OAUTH_CONFIGURATION_OF_THE_PACKRetrieve the OAuth configuration of the Pack for display purpose. Secrets will be returned with masks.
Input parameters
ID of a Pack
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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. Not all packs use system authentication - many use per-user authentication instead. Common error cases: - 400: Pack exists but hasn't been uploaded with a version yet, or system authentication isn't configured - 404: Pack doesn't exist or doesn't have system connection authentication
Input parameters
ID of the Pack to retrieve system connection metadata for. Must be a Pack you own or have appropriate access to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 matches against user names, email addresses, and group names. Results are limited to 20 users and 20 groups maximum. Use this action when you need to find people or groups to share a document with, or when building permission management workflows. Note: If no query is provided or the query is empty/whitespace-only, no results will be returned.
Input parameters
The ID of the Coda document to search principals for. Must be a valid document ID that the authenticated user has access to.
Search term to find users and groups. Can match names, email addresses, or parts thereof. Case-insensitive. Leading/trailing whitespace is automatically trimmed. If empty or None, no results are returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 authorizationUrl and tokenUrl. You must obtain these credentials by registering your application with the OAuth provider (e.g., Google, GitHub, Salesforce). Note: This sets the *credentials* for an OAuth-enabled Pack, not the OAuth configuration itself (authorizationUrl, tokenUrl, scopes), which are defined in the Pack's source code. Returns a request ID for tracking the configuration status. Changes may take a few moments to propagate.
Input parameters
ID of a Pack
The OAuth2 client ID for this Pack. This ID is obtained when you register your application with the OAuth provider's developer portal. It identifies your Pack to the OAuth provider during the authorization flow.
The OAuth2 redirect URI (callback URL) for this Pack. This is the URL where users will be redirected after authorizing your Pack. For Coda Packs, this is typically a Coda-provided URL. The redirect URI must match exactly what you configured in the OAuth provider's application settings.
The OAuth2 client secret for this Pack. This secret is obtained alongside the client ID when registering your application with the OAuth provider. It is used to securely authenticate token exchange requests. Keep this value confidential as it grants access to your Pack's OAuth credentials.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 configured with system-level authentication, where the Pack maker's credentials are used for all users rather than per-user authentication. Prerequisites: - The Pack must have at least one version uploaded before credentials can be set - The Pack's source code must define system authentication (e.g., via setSystemAuthentication()) - You must be the owner or have appropriate permissions for the Pack Note: This is a destructive operation that replaces all existing credentials. Use PATCH (/packs/{packId}/systemConnection) to update specific credential fields instead.
Input parameters
ID of a Pack. The Pack must have at least one version uploaded before system connection credentials can be set.
Credentials for the Pack's system connection. The structure depends on the authentication type configured in the Pack's source code (e.g., OAuth2ClientCredentials, HeaderBearerToken, WebBasic, CustomAuthentication, etc.). Common fields include 'token', 'client_id', 'client_secret', 'username', 'password', 'api_key', etc. This completely replaces any existing credentials.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 its configured steps asynchronously. The response includes a requestId that can be used with the get_mutation_status action to check if the automation has completed. Important: The automation rule ID must be obtained manually from the Coda UI with Developer Mode enabled. There is currently no API endpoint to list automation rules programmatically.
Input parameters
ID of the doc containing the webhook-triggered automation. Example: 'AbCDeFGH'. You can get this from the list_available_docs action or from the doc's browser URL.
ID of the webhook-triggered automation rule to trigger. To obtain this ID: 1) Enable Developer Mode in your Coda account settings (Labs > Enable Developer Mode), 2) Navigate to the automation in your doc, 3) Click the three-dots menu on the automation rule to view its ID. The automation must be configured as 'Webhook invoked' type. Example: 'grid-auto-AbCdEfGh'.
Optional JSON payload to pass to the webhook automation. This data will be available in the automation's steps as 'Step 1 Result'. You can include any JSON-serializable data (strings, numbers, booleans, objects, arrays). Example: {'message': 'Hello from API', 'count': 42, 'tags': \['urgent', 'test'\]}
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 is already unpublished (idempotent). Note that this is a destructive operation that affects document visibility.
Input parameters
ID of the doc to unpublish. This is the unique identifier for the Coda document (e.g., 'pXsafDTyh1'). The document must exist and be accessible by the authenticated user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 can copy the document - Whether viewers can request editing access You can update one or multiple settings in a single request. Settings not specified in the request will retain their current values. Returns the complete set of ACL settings after the update.
Input parameters
The ID of the Coda document whose ACL settings should be updated. Example: 'AbCDeFGH'
Controls whether viewers can make copies of the document. When true, anyone with view access can create their own copy. When false, copying is restricted. Leave unset to keep current value.
Controls whether viewers can request edit access to the document. When true, viewers see a button to request editing permissions from the owner. When false, viewers cannot request access upgrades. Leave unset to keep current value.
Controls whether editors can modify document permissions. When true, editors can invite others and change sharing settings. When false, only the document owner can change permissions. Leave unset to keep current value.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
The ID of the Pack to update the release for.
Updated release notes describing key features, changes, or fixes in this release. Use this to communicate important information to Pack users.
The ID of the Pack release to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
New name for the page. Note: Updating the page name requires Doc Maker permissions.
ID of the doc containing the page to update.
Name of the icon to use for the page. Can be a standard Coda icon name (e.g., 'rocket', 'star') or a custom icon reference. Requires Doc Maker permissions.
URL of the cover image to use for the page.
Whether the page should be hidden. Note: Some pages cannot be hidden (e.g., the sole top-level page in a doc), and this setting will be ignored for those pages.
New subtitle for the page.
ID or name of the page to update. Page IDs are recommended over names as names can be easily changed by users. If using a name, URI-encode it. If multiple pages have the same name, an arbitrary one will be selected.
Content update configuration for appending or inserting content into a page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 the applicable workspace. The API returns an empty response on success - use CODA_GET_INFO_ABOUT_A_DOC to verify changes.
Input parameters
The unique identifier of the document to update. You can obtain this from the CODA_LIST_AVAILABLE_DOCS or CODA_CREATE_DOC actions.
The new title/name for the document. If not provided, the document title remains unchanged.
The name of the icon to display for the document. Common icon names include: 'rocket', 'star', 'lightbulb', 'calendar', 'coda', etc. If not provided, the document icon remains unchanged.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 append). Requirements: - You must be the pack owner to update featured docs - Exactly one doc in the items list must have isPinned=true - All doc URLs must be published doc URLs (e.g., https://coda.io/@username/doc-name) - Regular browser links will cause a 400 error On success, returns an empty JSON object {}.
Input parameters
A list of docs to set as the featured docs for a Pack. This replaces the existing featured docs list. Exactly one doc must have isPinned=true. Each doc URL must be a published doc URL (e.g., https://coda.io/@username/doc-name).
The unique numeric identifier of the Pack. You must be the pack owner to update featured docs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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.
Input parameters
Name of the folder.
ID of the folder to update.
Description of the folder.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_UPDATE_PACKUpdate an existing Pack for non-versioned fields.
Input parameters
The name of the Pack.
ID of a Pack
The full description of the Pack.
The asset id of the Pack"s logo, returned by \[`#PackAssetUploadComplete`\](#operation/packAssetUploadComplete) endpoint.
The asset id of the Pack"s cover image, returned by \[`#PackAssetUploadComplete`\](#operation/packAssetUploadComplete) endpoint.
A contact email for the Pack.
The example images for the Pack.
A Privacy Policy URL for the Pack.
A short version of the description of the Pack.
A Terms of Service URL for the Pack.
Visibility of a pack"s source code.
The rate limit interval in seconds.
The maximum number of Pack operations that can be performed in a given interval.
The rate limit interval in seconds.
The maximum number of Pack operations that can be performed in a given interval.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_UPDATE_ROWDEPRECATED: Use CODA_UPSERT_ROWS instead. Tool to update an existing row in a Coda table. Use when you need to modify specific cell values in a row. This endpoint returns a 202 status code indicating the update has been queued and will be processed within seconds.
Input parameters
Row object containing the cells to update.
ID of the doc containing the table.
ID or name of the row to update. Using row IDs is recommended. If using a name and multiple rows have the same value in the identifying column, an arbitrary one will be selected.
If true, the API will not attempt to parse the data in any way.
ID or name of the table. Using table IDs is recommended to avoid issues if table names change.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_UPDATES_A_CUSTOM_DOMAINUpdates properties of a document's custom domain.
Input parameters
ID of the doc.
A custom domain for a published doc.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_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 organization (Enterprise feature) - The requesting user must have Admin permissions in the workspace - The target user must already be a member of the workspace **Note:** This endpoint will return a 400 error with message "Workspace does not belong to an organization" if used with a non-Enterprise workspace.
Input parameters
Email address of the user whose role you want to update.
The new workspace role to assign to the user. Must be one of: 'Admin' (full workspace admin access), 'DocMaker' (can create and edit docs), or 'Editor' (can edit but not create docs).
ID of the workspace (must belong to an organization). Use CODA_GET_USER_INFO to get your workspace ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_UPLOAD_A_PACK_ASSETRequest a signed s3 URL to upload your Pack asset.
Input parameters
ID of a Pack
Filename
The media type of the image being sent.
The SHA-256 hash of the image to be uploaded.
Packassettype
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_UPLOAD_PACK_SOURCE_CODERequest a signed s3 URL to upload your Pack source code.
Input parameters
ID of a Pack
Filename
Packversion
The SHA-256 hash of the image to be uploaded.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CODA_UPSERT_ROWSThis 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 without creating duplicates.
Input parameters
Array of row objects to insert or upsert. When row_id_or_name is provided, only the first row in the array is used.
ID of the doc containing the table.
Optional array of column IDs/names to use as upsert keys. If provided, existing rows matching these keys will be updated. Ignored when row_id_or_name is provided.
ID or name of a specific row to update. When provided, only the first item in 'rows' is used and a PUT request is made to update that specific row. Using row IDs is recommended to avoid issues if row names change.
If true, the API will not attempt to parse the data in any way.
ID or name of the table. Using table IDs is recommended to avoid issues if table names change.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 67 agents privately built on Nagent that already use Coda.
Build on Nagent
Connect Coda to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Coda, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Coda is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Coda is connected, you configure its 110 actions and 4 triggers directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Coda steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Coda event fires, the agent kicks off automatically.
Every Coda action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Coda ships with 110 pre-built productivity actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Coda together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Coda-based workflows tailored to your business.