coda-automation
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.zipInstalls 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.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
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_CONNECTIONSwith toolkitcoda - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcoda - 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_DOCSorCODA_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 documentsisOwner: Filter to docs owned by the userdocId: Document ID for page operationspageIdOrName: Page identifier or nameurl: Browser URL for resolve operations
Pitfalls:
- Document IDs are alphanumeric strings (e.g., 'AbCdEfGhIj')
CODA_RESOLVE_BROWSER_LINKis 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 tabletableIdOrName: Table identifier or namequery: Filter query for searching rowsrows: Array of row objects for upsert operationskeyColumns: Column IDs used for matching during upsertsortBy: Column to sort results byuseColumnNames: Use column names instead of IDs in row data
Pitfalls:
- Table names may contain spaces; URL-encode if needed
CODA_UPSERT_ROWSdoes insert if no match onkeyColumns, update if match foundkeyColumnsmust 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: trueallows 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 IDformulaIdOrName: 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 exportoutputFormat: 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
statusis '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 IDaccess: Permission level ('readonly', 'write', 'comment')principal: Object with email or user ID of the recipientsuppressEmail: Whether to skip the sharing notification email
Pitfalls:
- Permission levels: 'readonly', 'write', 'comment'
- Adding permission sends an email notification by default; use
suppressEmailto 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 IDslug: Custom URL slug for the published doccategoryIds: 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
pageTokenin 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.
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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| coda-automation (this skill) | 0 | 5mo | No flags | Intermediate |
| linear | 10 | 2mo | No flags | Beginner |
| zapier-workflows | 11 | 9mo | Review | Beginner |
| attio-skill-generator | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by diegosouzapw
View all by diegosouzapw →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.
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.
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.
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.
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".
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.