Coda Automation via Rube MCP
Automate Coda document and data operations through Composio's Coda toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Coda connection via
RUBE_MANAGE_CONNECTIONS with toolkit coda
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit coda
- If connection is not ACTIVE, follow the returned auth link to complete Coda authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Search and Browse Documents
When to use: User wants to find, list, or inspect Coda documents
Tool sequence:
CODA_SEARCH_DOCS or CODA_LIST_AVAILABLE_DOCS - Find documents [Required]
CODA_RESOLVE_BROWSER_LINK - Resolve a Coda URL to doc/page/table IDs [Alternative]
CODA_LIST_PAGES - List pages within a document [Optional]
CODA_GET_A_PAGE - Get specific page details [Optional]
Key parameters:
query: Search term for finding documents
isOwner: Filter to docs owned by the user
docId: Document ID for page operations
pageIdOrName: Page identifier or name
url: Browser URL for resolve operations
Pitfalls:
- Document IDs are alphanumeric strings (e.g., 'AbCdEfGhIj')
CODA_RESOLVE_BROWSER_LINK is the best way to convert a Coda URL to API IDs
- Page names may not be unique within a doc; prefer page IDs
- Search results include docs shared with the user, not just owned docs
2. Work with Tables and Data
When to use: User wants to read, write, or query table data
Tool sequence:
CODA_LIST_TABLES - List tables in a document [Prerequisite]
CODA_LIST_COLUMNS - Get column definitions for a table [Prerequisite]
CODA_LIST_TABLE_ROWS - List all rows with optional filters [Required]
CODA_SEARCH_ROW - Search for specific rows by query [Alternative]
CODA_GET_A_ROW - Get a specific row by ID [Optional]
CODA_UPSERT_ROWS - Insert or update rows in a table [Optional]
CODA_GET_A_COLUMN - Get details of a specific column [Optional]
Key parameters:
docId: Document ID containing the table
tableIdOrName: Table identifier or name
query: Filter query for searching rows
rows: Array of row objects for upsert operations
keyColumns: Column IDs used for matching during upsert
sortBy: Column to sort results by
useColumnNames: Use column names instead of IDs in row data
Pitfalls:
- Table names may contain spaces; URL-encode if needed
CODA_UPSERT_ROWS does insert if no match on keyColumns, update if match found
keyColumns must reference columns that have unique values for reliable upserts
- Column IDs are different from column names; list columns first to map names to IDs
useColumnNames: true allows using human-readable names in row data
- Row data values must match the column type (text, number, date, etc.)
3. Manage Formulas
When to use: User wants to list or evaluate formulas in a document
Tool sequence:
CODA_LIST_FORMULAS - List all named formulas in a doc [Required]
CODA_GET_A_FORMULA - Get a specific formula's current value [Optional]
Key parameters:
docId: Document ID
formulaIdOrName: Formula identifier or name
Pitfalls:
- Formulas are named calculations defined in the document
- Formula values are computed server-side; results reflect the current state
- Formula names are case-sensitive
4. Export Document Content
When to use: User wants to export a document or page to HTML or Markdown
Tool sequence:
CODA_BEGIN_CONTENT_EXPORT - Start an export job [Required]
CODA_CONTENT_EXPORT_STATUS - Poll export status until complete [Required]
Key parameters:
docId: Document ID to export
outputFormat: Export format ('html' or 'markdown')
pageIdOrName: Specific page to export (optional, omit for full doc)
requestId: Export request ID for status polling
Pitfalls:
- Export is asynchronous; poll status until
status is 'complete'
- Large documents may take significant time to export
- Export URL in the completed response is temporary; download promptly
- Polling too frequently may hit rate limits; use 2-5 second intervals
5. Manage Permissions and Sharing
When to use: User wants to view or manage document access
Tool sequence:
CODA_GET_SHARING_METADATA - View current sharing settings [Required]
CODA_GET_ACL_SETTINGS - Get access control list settings [Optional]
CODA_ADD_PERMISSION - Grant access to a user or email [Optional]
Key parameters:
docId: Document ID
access: Permission level ('readonly', 'write', 'comment')
principal: Object with email or user ID of the recipient
suppressEmail: Whether to skip the sharing notification email
Pitfalls:
- Permission levels: 'readonly', 'write', 'comment'
- Adding permission sends an email notification by default; use
suppressEmail to prevent
- Cannot remove permissions via API in all cases; check ACL settings
6. Publish and Customize Documents
When to use: User wants to publish a document or manage custom domains
Tool sequence:
CODA_PUBLISH_DOC - Publish a document publicly [Required]
CODA_UNPUBLISH_DOC - Unpublish a document [Optional]
CODA_ADD_CUSTOM_DOMAIN - Add a custom domain for published doc [Optional]
CODA_GET_DOC_CATEGORIES - Get doc categories for discovery [Optional]
Key parameters:
docId: Document ID
slug: Custom URL slug for the published doc
categoryIds: Category IDs for discoverability
Pitfalls:
- Publishing makes the document accessible to anyone with the link
- Custom domains require DNS configuration
- Unpublishing removes public access but retains shared access
Common Patterns
ID Resolution
Doc URL -> Doc ID:
1. Call CODA_RESOLVE_BROWSER_LINK with the Coda URL
2. Extract docId from the response
Table name -> Table ID:
1. Call CODA_LIST_TABLES with docId
2. Find table by name, extract id
Column name -> Column ID:
1. Call CODA_LIST_COLUMNS with docId and tableIdOrName
2. Find column by name, extract id
Pagination
- Coda uses cursor-based pagination with
pageToken
- Check response for
nextPageToken
- Pass as
pageToken in next request until absent
- Default page sizes vary by endpoint
Row Upsert Pattern
1. Call CODA_LIST_COLUMNS to get column IDs
2. Build row objects with column ID keys and values
3. Set keyColumns to unique identifier column(s)
4. Call CODA_UPSERT_ROWS with rows and keyColumns
Known Pitfalls
ID Formats:
- Document IDs: alphanumeric strings
- Table/column/row IDs: prefixed strings (e.g., 'grid-abc', 'c-xyz')
- Use RESOLVE_BROWSER_LINK to convert URLs to IDs
Data Types:
- Row values must match column types
- Date columns expect ISO 8601 format
- Select/multi-select columns expect exact option values
- People columns expect email addresses
Rate Limits:
- Coda API has per-token rate limits
- Implement backoff on 429 responses
- Bulk row operations via UPSERT_ROWS are more efficient than individual updates
Quick Reference
| Task |
Tool Slug |
Key Params |
| Search docs |
CODA_SEARCH_DOCS |
query |
| List docs |
CODA_LIST_AVAILABLE_DOCS |
isOwner |
| Resolve URL |
CODA_RESOLVE_BROWSER_LINK |
url |
| List pages |
CODA_LIST_PAGES |
docId |
| Get page |
CODA_GET_A_PAGE |
docId, pageIdOrName |
| List tables |
CODA_LIST_TABLES |
docId |
| List columns |
CODA_LIST_COLUMNS |
docId, tableIdOrName |
| List rows |
CODA_LIST_TABLE_ROWS |
docId, tableIdOrName |
| Search rows |
CODA_SEARCH_ROW |
docId, tableIdOrName, query |
| Get row |
CODA_GET_A_ROW |
docId, tableIdOrName, rowIdOrName |
| Upsert rows |
CODA_UPSERT_ROWS |
docId, tableIdOrName, rows, keyColumns |
| Get column |
CODA_GET_A_COLUMN |
docId, tableIdOrName, columnIdOrName |
| Push button |
CODA_PUSH_A_BUTTON |
docId, tableIdOrName, rowIdOrName, columnIdOrName |
| List formulas |
CODA_LIST_FORMULAS |
docId |
| Get formula |
CODA_GET_A_FORMULA |
docId, formulaIdOrName |
| Begin export |
CODA_BEGIN_CONTENT_EXPORT |
docId, outputFormat |
| Export status |
CODA_CONTENT_EXPORT_STATUS |
docId, requestId |
| Get sharing |
CODA_GET_SHARING_METADATA |
docId |
| Add permission |
CODA_ADD_PERMISSION |
docId, access, principal |
| Publish doc |
CODA_PUBLISH_DOC |
docId, slug |
| Unpublish doc |
CODA_UNPUBLISH_DOC |
docId |
| List packs |
CODA_LIST_PACKS |
(none) |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: coda-automation3description: "Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas."4risk: critical5source: community6date_added: "2026-02-27"7metadata:8 source: https://skillmd.com/skills/mhassan0000/coda-automation9---1011# Coda Automation via Rube MCP1213Automate Coda document and data operations through Composio's Coda toolkit via Rube MCP.1415## Prerequisites1617- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)18- Active Coda connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coda`19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2021## Setup2223**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2425261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coda`283. If connection is not ACTIVE, follow the returned auth link to complete Coda authentication294. Confirm connection status shows ACTIVE before running any workflows3031## Core Workflows3233### 1. Search and Browse Documents3435**When to use**: User wants to find, list, or inspect Coda documents3637**Tool sequence**:381. `CODA_SEARCH_DOCS` or `CODA_LIST_AVAILABLE_DOCS` - Find documents [Required]392. `CODA_RESOLVE_BROWSER_LINK` - Resolve a Coda URL to doc/page/table IDs [Alternative]403. `CODA_LIST_PAGES` - List pages within a document [Optional]414. `CODA_GET_A_PAGE` - Get specific page details [Optional]4243**Key parameters**:44- `query`: Search term for finding documents45- `isOwner`: Filter to docs owned by the user46- `docId`: Document ID for page operations47- `pageIdOrName`: Page identifier or name48- `url`: Browser URL for resolve operations4950**Pitfalls**:51- Document IDs are alphanumeric strings (e.g., 'AbCdEfGhIj')52- `CODA_RESOLVE_BROWSER_LINK` is the best way to convert a Coda URL to API IDs53- Page names may not be unique within a doc; prefer page IDs54- Search results include docs shared with the user, not just owned docs5556### 2. Work with Tables and Data5758**When to use**: User wants to read, write, or query table data5960**Tool sequence**:611. `CODA_LIST_TABLES` - List tables in a document [Prerequisite]622. `CODA_LIST_COLUMNS` - Get column definitions for a table [Prerequisite]633. `CODA_LIST_TABLE_ROWS` - List all rows with optional filters [Required]644. `CODA_SEARCH_ROW` - Search for specific rows by query [Alternative]655. `CODA_GET_A_ROW` - Get a specific row by ID [Optional]666. `CODA_UPSERT_ROWS` - Insert or update rows in a table [Optional]677. `CODA_GET_A_COLUMN` - Get details of a specific column [Optional]6869**Key parameters**:70- `docId`: Document ID containing the table71- `tableIdOrName`: Table identifier or name72- `query`: Filter query for searching rows73- `rows`: Array of row objects for upsert operations74- `keyColumns`: Column IDs used for matching during upsert75- `sortBy`: Column to sort results by76- `useColumnNames`: Use column names instead of IDs in row data7778**Pitfalls**:79- Table names may contain spaces; URL-encode if needed80- `CODA_UPSERT_ROWS` does insert if no match on `keyColumns`, update if match found81- `keyColumns` must reference columns that have unique values for reliable upserts82- Column IDs are different from column names; list columns first to map names to IDs83- `useColumnNames: true` allows using human-readable names in row data84- Row data values must match the column type (text, number, date, etc.)8586### 3. Manage Formulas8788**When to use**: User wants to list or evaluate formulas in a document8990**Tool sequence**:911. `CODA_LIST_FORMULAS` - List all named formulas in a doc [Required]922. `CODA_GET_A_FORMULA` - Get a specific formula's current value [Optional]9394**Key parameters**:95- `docId`: Document ID96- `formulaIdOrName`: Formula identifier or name9798**Pitfalls**:99- Formulas are named calculations defined in the document100- Formula values are computed server-side; results reflect the current state101- Formula names are case-sensitive102103### 4. Export Document Content104105**When to use**: User wants to export a document or page to HTML or Markdown106107**Tool sequence**:1081. `CODA_BEGIN_CONTENT_EXPORT` - Start an export job [Required]1092. `CODA_CONTENT_EXPORT_STATUS` - Poll export status until complete [Required]110111**Key parameters**:112- `docId`: Document ID to export113- `outputFormat`: Export format ('html' or 'markdown')114- `pageIdOrName`: Specific page to export (optional, omit for full doc)115- `requestId`: Export request ID for status polling116117**Pitfalls**:118- Export is asynchronous; poll status until `status` is 'complete'119- Large documents may take significant time to export120- Export URL in the completed response is temporary; download promptly121- Polling too frequently may hit rate limits; use 2-5 second intervals122123### 5. Manage Permissions and Sharing124125**When to use**: User wants to view or manage document access126127**Tool sequence**:1281. `CODA_GET_SHARING_METADATA` - View current sharing settings [Required]1292. `CODA_GET_ACL_SETTINGS` - Get access control list settings [Optional]1303. `CODA_ADD_PERMISSION` - Grant access to a user or email [Optional]131132**Key parameters**:133- `docId`: Document ID134- `access`: Permission level ('readonly', 'write', 'comment')135- `principal`: Object with email or user ID of the recipient136- `suppressEmail`: Whether to skip the sharing notification email137138**Pitfalls**:139- Permission levels: 'readonly', 'write', 'comment'140- Adding permission sends an email notification by default; use `suppressEmail` to prevent141- Cannot remove permissions via API in all cases; check ACL settings142143### 6. Publish and Customize Documents144145**When to use**: User wants to publish a document or manage custom domains146147**Tool sequence**:1481. `CODA_PUBLISH_DOC` - Publish a document publicly [Required]1492. `CODA_UNPUBLISH_DOC` - Unpublish a document [Optional]1503. `CODA_ADD_CUSTOM_DOMAIN` - Add a custom domain for published doc [Optional]1514. `CODA_GET_DOC_CATEGORIES` - Get doc categories for discovery [Optional]152153**Key parameters**:154- `docId`: Document ID155- `slug`: Custom URL slug for the published doc156- `categoryIds`: Category IDs for discoverability157158**Pitfalls**:159- Publishing makes the document accessible to anyone with the link160- Custom domains require DNS configuration161- Unpublishing removes public access but retains shared access162163## Common Patterns164165### ID Resolution166167**Doc URL -> Doc ID**:168```1691. Call CODA_RESOLVE_BROWSER_LINK with the Coda URL1702. Extract docId from the response171```172173**Table name -> Table ID**:174```1751. Call CODA_LIST_TABLES with docId1762. Find table by name, extract id177```178179**Column name -> Column ID**:180```1811. Call CODA_LIST_COLUMNS with docId and tableIdOrName1822. Find column by name, extract id183```184185### Pagination186187- Coda uses cursor-based pagination with `pageToken`188- Check response for `nextPageToken`189- Pass as `pageToken` in next request until absent190- Default page sizes vary by endpoint191192### Row Upsert Pattern193194```1951. Call CODA_LIST_COLUMNS to get column IDs1962. Build row objects with column ID keys and values1973. Set keyColumns to unique identifier column(s)1984. Call CODA_UPSERT_ROWS with rows and keyColumns199```200201## Known Pitfalls202203**ID Formats**:204- Document IDs: alphanumeric strings205- Table/column/row IDs: prefixed strings (e.g., 'grid-abc', 'c-xyz')206- Use RESOLVE_BROWSER_LINK to convert URLs to IDs207208**Data Types**:209- Row values must match column types210- Date columns expect ISO 8601 format211- Select/multi-select columns expect exact option values212- People columns expect email addresses213214**Rate Limits**:215- Coda API has per-token rate limits216- Implement backoff on 429 responses217- Bulk row operations via UPSERT_ROWS are more efficient than individual updates218219## Quick Reference220221| Task | Tool Slug | Key Params |222|------|-----------|------------|223| Search docs | CODA_SEARCH_DOCS | query |224| List docs | CODA_LIST_AVAILABLE_DOCS | isOwner |225| Resolve URL | CODA_RESOLVE_BROWSER_LINK | url |226| List pages | CODA_LIST_PAGES | docId |227| Get page | CODA_GET_A_PAGE | docId, pageIdOrName |228| List tables | CODA_LIST_TABLES | docId |229| List columns | CODA_LIST_COLUMNS | docId, tableIdOrName |230| List rows | CODA_LIST_TABLE_ROWS | docId, tableIdOrName |231| Search rows | CODA_SEARCH_ROW | docId, tableIdOrName, query |232| Get row | CODA_GET_A_ROW | docId, tableIdOrName, rowIdOrName |233| Upsert rows | CODA_UPSERT_ROWS | docId, tableIdOrName, rows, keyColumns |234| Get column | CODA_GET_A_COLUMN | docId, tableIdOrName, columnIdOrName |235| Push button | CODA_PUSH_A_BUTTON | docId, tableIdOrName, rowIdOrName, columnIdOrName |236| List formulas | CODA_LIST_FORMULAS | docId |237| Get formula | CODA_GET_A_FORMULA | docId, formulaIdOrName |238| Begin export | CODA_BEGIN_CONTENT_EXPORT | docId, outputFormat |239| Export status | CODA_CONTENT_EXPORT_STATUS | docId, requestId |240| Get sharing | CODA_GET_SHARING_METADATA | docId |241| Add permission | CODA_ADD_PERMISSION | docId, access, principal |242| Publish doc | CODA_PUBLISH_DOC | docId, slug |243| Unpublish doc | CODA_UNPUBLISH_DOC | docId |244| List packs | CODA_LIST_PACKS | (none) |245246## When to Use247This skill is applicable to execute the workflow or actions described in the overview.248249## Limitations250- Use this skill only when the task clearly matches the scope described above.251- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.252- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.