Automates Coda doc operations (pages, tables, data) using the Rube MCP/Composio integration.

Install

mkdir -p .claude/skills/coda-automation-diegosouzapw && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16969" && unzip -o skill.zip -d .claude/skills/coda-automation-diegosouzapw && rm skill.zip

Installs to .claude/skills/coda-automation-diegosouzapw

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.
164 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Search for Coda documents by query or ownership
  • List pages within a specified Coda document
  • Read and write data in Coda tables
  • Manage formulas by listing or evaluating them
  • Export Coda document content to HTML or Markdown
  • Manage document permissions and sharing settings

How it works

This skill uses Composio's Coda toolkit via Rube MCP to interact with Coda documents, tables, and permissions. It performs operations like searching documents, listing pages, managing table data, evaluating formulas, exporting content, and setting permissions.

Inputs & outputs

You give it
Coda document ID and table ID, with row objects for upsert operations
You get back
Updated Coda table with inserted or modified rows

When to use coda-automation

  • Manage Coda tables
  • Update document rows
  • List and search pages
  • Automate doc publishing

About this skill

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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit coda
  3. If connection is not ACTIVE, follow the returned auth link to complete Coda authentication
  4. 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:

  1. CODA_SEARCH_DOCS or CODA_LIST_AVAILABLE_DOCS - Find documents [Required]
  2. CODA_RESOLVE_BROWSER_LINK - Resolve a Coda URL to doc/page/table IDs [Alternative]
  3. CODA_LIST_PAGES - List pages within a document [Optional]
  4. 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:

  1. CODA_LIST_TABLES - List tables in a document [Prerequisite]
  2. CODA_LIST_COLUMNS - Get column definitions for a table [Prerequisite]
  3. CODA_LIST_TABLE_ROWS - List all rows with optional filters [Required]
  4. CODA_SEARCH_ROW - Search for specific rows by query [Alternative]
  5. CODA_GET_A_ROW - Get a specific row by ID [Optional]
  6. CODA_UPSERT_ROWS - Insert or update rows in a table [Optional]
  7. 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:

  1. CODA_LIST_FORMULAS - List all named formulas in a doc [Required]
  2. 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:

  1. CODA_BEGIN_CONTENT_EXPORT - Start an export job [Required]
  2. 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:

  1. CODA_GET_SHARING_METADATA - View current sharing settings [Required]
  2. CODA_GET_ACL_SETTINGS - Get access control list settings [Optional]
  3. 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:

  1. CODA_PUBLISH_DOC - Publish a document publicly [Required]
  2. CODA_UNPUBLISH_DOC - Unpublish a document [Optional]
  3. CODA_ADD_CUSTOM_DOMAIN - Add a custom domain for published doc [Optional]
  4. 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

TaskTool SlugKey Params
Search docsCODA_SEARCH_DOCSquery
List docsCODA_LIST_AVAILABLE_DOCSisOwner
Resolve URLCODA_RESOLVE_BROWSER_LINKurl
List pagesCODA_LIST_PAGESdocId
Get pageCODA_GET_A_PAGEdocId, pageIdOrName
List tablesCODA_LIST_TABLESdocId
List columnsCODA_LIST_COLUMNSdocId, tableIdOrName
List rowsCODA_LIST_TABLE_ROWSdocId, tableIdOrName
Search rowsCODA_SEARCH_ROWdocId, tableIdOrName, query
Get rowCODA_GET_A_ROWdocId, tableIdOrName, rowIdOrName
Upsert rowsCODA_UPSERT_ROWSdocId, tableIdOrName, rows, keyColumns
Get columnCODA_GET_A_COLUMNdocId, tableIdOrName, columnIdOrName
Push buttonCODA_PUSH_A_BUTTONdocId, tableIdOrName, rowIdOrName, columnIdOrName
List formulasCODA_LIST_FORMULASdocId
Get formulaCODA_GET_A_FORMULAdocId, formulaIdOrName
Begin exportCODA_BEGIN_CONTENT_EXPORTdocId, outputFormat
Export statusCODA_CONTENT_EXPORT_STATUSdocId, requestId
Get sharingCODA_GET_SHARING_METADATAdocId
Add permissionCODA_ADD_PERMISSIONdocId, access, principal
Publish docCODA_PUBLISH_DOCdocId, slug
Unpublish docCODA_UNPUBLISH_DOCdocId
List packsCODA_LIST_PACKS(none)

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

When not to use it

  • When Coda is not the platform for document and data operations
  • When Rube MCP is not connected or available
  • When an active Coda connection is not established

Prerequisites

Rube MCPCoda connection

Limitations

  • Document IDs are alphanumeric strings, not human-readable names
  • Page names may not be unique within a document
  • Table names may contain spaces and require URL-encoding

How it compares

This skill automates Coda operations through a structured toolkit, whereas manual interaction would involve direct use of the Coda interface for each task.

Compared to similar skills

coda-automation side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
coda-automation (this skill)05moNo flagsIntermediate
linear102moNo flagsBeginner
zapier-workflows119moReviewBeginner
attio-skill-generator77moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by diegosouzapw

View all by diegosouzapw

helm-chart-scaffolding-v2

diegosouzapw

Helm Chart Scaffolding workflow skill. Use this skill when the user needs Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications and the operator should preserve the upstream workflow, copied support files, and provenance before

00

cc-skill-coding-standards-v2

diegosouzapw

Coding Standards & Best Practices workflow skill. Use this skill when the user needs Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development and the operator should preserve the upstream workflow, copied support files, and provenance before

00

worktree-setup

diegosouzapw

Automatically invoked after `git worktree add` to create data/shared symlink and data/local directory. Required before starting work in any new worktree.

00

parsehub-automation

diegosouzapw

Automate Parsehub tasks via Rube MCP (Composio). Always search tools first for current schemas.

00

signalwire-agents-sdk

diegosouzapw

Expert assistance for building SignalWire AI Agents in Python. Automatically activates when working with AgentBase, SWAIG functions, skills, SWML, voice configuration, DataMap, or any signalwire_agents code. Provides patterns, best practices, and complete working examples.

00

agent-sales-engineer

diegosouzapw

Expert sales engineer specializing in technical pre-sales, solution architecture, and proof of concepts. Masters technical demonstrations, competitive positioning, and translating complex technology into business value for prospects and customers.

00

You might also like

linear

lobehub

Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.

10117

zapier-workflows

davila7

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

11101

attio-skill-generator

kesslerio

Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.

7100

automation-brainstorm

MacroMan5

Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.

778

daily-briefing

anthropics

Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".

761

jira

davila7

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

1152

Search skills

Search the agent skills registry