- Category: productivity
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 110
- Triggers: 4
- Slug:
CODA - Version: 20261101_00
Tools
Add a category for pack
Add a category for pack
Add a maker for pack
Add a maker for pack
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
Output
Add a permission for pack
Add a permission for pack
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
Output
Add custom domain
Add custom domain
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
Output
Add permission
Add permission
CODA_ADD_PERMISSIONAdds a new permission to the doc.Input Parameters
Output
Begin content export
Begin content export
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
Output
Content export status
Content export status
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
Output
Copy Document
Copy Document
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
Output
Create a new pack release
Create a new pack release
Create a page
Create a page
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
Output
Create doc
Create doc
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
folderId query parameter.Output
Create Folder
Create Folder
Create Pack
Create Pack
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 useInput Parameters
Output
Create Pack Invitation
Create Pack Invitation
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
Output
Delete a category for pack
Delete a category for pack
Delete a maker for pack
Delete a maker for pack
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
Output
Delete a page
Delete a page
CODA_DELETE_A_PAGEDeletes the specified page.Input Parameters
Output
Delete a permission for pack
Delete a permission for pack
Delete doc
Delete doc
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 docInput Parameters
Output
Delete Folder
Delete Folder
Delete multiple rows
Delete multiple rows
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
Output
Delete pack
Delete pack
Delete Pack listing draft
Delete Pack listing draft
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
Output
Delete Page Content
Delete Page Content
CODA_DELETE_PAGE_CONTENTDelete specific content elements or all content from a Coda page; omitting element IDs or providing an empty list deletes all page content. The deletion is queued for processing.Input Parameters
Output
Delete permission
Delete permission
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
Output
Delete row
Delete row
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
Output
Deletes a custom domain
Deletes a custom domain
Fetch grouped logs by pack org root ingestion id
Fetch grouped logs by pack org root ingestion id
CODA_FETCH_GROUPED_LOGS_BY_PACK_ORG_ROOT_INGESTION_IDRetrieves grouped logs for a Pack ingestion for debugging, with optional filtering and pagination. A 404 response is returned as an empty list, so an empty result does not distinguish a missing resource from a response with no logs.Input Parameters
Output
Fetch ingestion executions for pack
Fetch ingestion executions for pack
CODA_FETCH_INGESTION_EXECUTIONS_FOR_PACKRetrieves ingestion executions for a Pack and root ingestion for debugging, with optional filtering and pagination. A 404 response is returned as an empty list, so an empty result does not distinguish a missing resource from a response with no executions.Input Parameters
Output
Get acl settings
Get acl settings
Get a column
Get a column
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 informationInput Parameters
Output
Get a control
Get a control
Get a formula
Get a formula
Get analytics last updated day
Get analytics last updated day
Get a page
Get a page
CODA_GET_A_PAGEReturns details about a page.Input Parameters
Output
Get a row
Get a row
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
Output
Get Pack details by ID
Get Pack details by ID
CODA_GET_A_SINGLE_PACKRetrieves details of a specific Coda Pack by its ID, including its name, description, workspace, and available logo and rate-limit information.Input Parameters
Output
Get a table
Get a table
CODA_GET_A_TABLEReturns details about a specific table or view.Input Parameters
layout field of detail and form layouts respectively (instead of “masterDetail” for both)Output
Get detailed listing information for a pack
Get detailed listing information for a pack
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
Output
Get doc analytics summary
Get doc analytics summary
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
Output
Get doc categories
Get doc categories
Get folder
Get folder
Get info about a doc
Get info about a doc
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
Output
Get mutation status
Get mutation status
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 pendingInput Parameters
Output
Get pack analytics summary
Get pack analytics summary
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
Output
Gets custom doc domains providers
Gets custom doc domains providers
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
Output
Get sharing metadata
Get sharing metadata
Gets the json schema for pack configuration
Gets the json schema for pack configuration
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
Output
Get the difference between two pack versions
Get the difference between two pack versions
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
Output
Get the next valid version for a pack
Get the next valid version for a pack
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
Output
Get the source code for a pack version
Get the source code for a pack version
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
Output
Get user info
Get user info
List available docs
List available docs
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
Output
List categories for pack
List categories for pack
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
Output
List columns
List columns
CODA_LIST_COLUMNSReturns a list of columns in a table.Input Parameters
Output
List controls
List controls
List custom doc domains
List custom doc domains
CODA_LIST_CUSTOM_DOC_DOMAINSLists custom domains configured for a published Coda document, including their setup and connection status. The response may include a link or token for another page.Input Parameters
Output
List doc analytics
List doc analytics
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
Output
List featured docs for a pack
List featured docs for a pack
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
Output
List Folders
List Folders
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
Output
List formulas
List formulas
List makers for pack
List makers for pack
List pack analytics
List pack analytics
CODA_LIST_PACK_ANALYTICSLists analytics for Packs the user can edit, including installation counts and invocation metrics. Supports workspace and date filters, sorting, and pagination.Input Parameters
Output
List pack formula analytics
List pack formula analytics
CODA_LIST_PACK_FORMULA_ANALYTICSReturns analytics data for Pack formulas.Input Parameters
packFormulaNames. If specified, this must have the same length as packFormulaNames.Output
List packs
List packs
List page analytics
List page analytics
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
Output
List Page Content
List Page Content
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
Output
List permissions
List permissions
List permissions for a pack
List permissions for a pack
List table rows
List table rows
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
<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").Output
List tables
List tables
List the pack listings accessible to a user
List the pack listings accessible to a user
CODA_LIST_THE_PACK_LISTINGS_ACCESSIBLE_TO_A_USERGet listings of public Packs and Packs created by you.Input Parameters
Output
List the releases for a pack
List the releases for a pack
List the versions for a pack
List the versions for a pack
List User Pack Invitations
List User Pack Invitations
List workspace roles
List workspace roles
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
Output
List workspace users
List workspace users
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
Output
Pack asset upload complete
Pack asset upload complete
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
Output
Pack source code upload complete
Pack source code upload complete
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
Output
Pack version upload complete
Pack version upload complete
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
Output
Patch the system connection credentials of the pack
Patch the system connection credentials of the pack
Publish doc
Publish doc
Register pack version
Register pack version
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
Output
Resolve browser link
Resolve browser link
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
Output
Retrieve the grouped logs of a pack
Retrieve the grouped logs of a pack
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
Output
Retrieve the information for a specific log
Retrieve the information for a specific log
CODA_RETRIEVE_THE_INFORMATION_FOR_A_SPECIFIC_LOGRetrieves details for a specific Pack ingestion log using an organization, ingestion, log, and details key. A 404 produces found=False; other error statuses raise an error.Input Parameters
Output
Retrieve the logs of a ingestion
Retrieve the logs of a ingestion
CODA_RETRIEVE_THE_LOGS_OF_A_INGESTIONRetrieves Pack ingestion logs for debugging, with filtering and pagination. A 404 produces an empty result; other error statuses raise an error.Input Parameters
Output
Retrieve the logs of a pack
Retrieve the logs of a pack
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
Output
Retrieve the oauth configuration of the pack
Retrieve the oauth configuration of the pack
Retrieve the system connection metadata of the pack
Retrieve the system connection metadata of the pack
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 authenticationInput Parameters
Output
Search principals
Search principals
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
Output
Set the oauth configurations of the pack
Set the oauth configurations of the pack
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
Output
Set the system connection credentials of the pack
Set the system connection credentials of the pack
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
Output
Trigger automation
Trigger automation
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
Output
Unpublish doc
Unpublish doc
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
Output
Update acl settings
Update acl settings
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
Output
Update an existing Pack release
Update an existing Pack release
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
Output
Update a page
Update a page
CODA_UPDATE_A_PAGEUpdate a page’s properties or append HTML or Markdown content. Updating a page title or icon requires you to be a Doc Maker in the applicable workspace.Input Parameters
Output
Update doc
Update doc
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
Output
Update featured docs for a pack
Update featured docs for a pack
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
Output
Update Folder
Update Folder
Update pack
Update pack
Update Row in Coda Table (Deprecated)
Update Row in Coda Table (Deprecated)
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
Output
Updates a custom domain
Updates a custom domain
Updates user role
Updates user role
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
Output
Upload a pack asset
Upload a pack asset
Upload pack source code
Upload pack source code
Insert/Update Rows in Coda Table
Insert/Update Rows in Coda Table
CODA_UPSERT_ROWSInsert or upsert rows in a Coda table using optional key columns, or update a specific row by ID or name. When a specific row is supplied, only the first submitted row is used and key columns are ignored.Input Parameters
Output
Triggers
Coda Document Deleted Trigger
Coda Document Deleted Trigger
New Coda Document Trigger
New Coda Document Trigger
New Coda Page Trigger
New Coda Page Trigger