PPlatformAppStores

Coda Packs

Productivity

Coda (Coda Project, Inc.) · Productivity & collaboration suites

Best for: Developers who want to add third-party integrations and custom logic into Coda docs quickly.

Overview

Coda Packs extend Coda docs with new building blocks — custom formulas, sync tables that pull external data, actions that push changes back, and column formats — all written in JavaScript/TypeScript. Builders use the browser-based Pack Studio or a developer CLI; Coda deploys and hosts the Pack, so there is no infrastructure to run. Authentication is configured per Pack, most commonly OAuth 2.0 so each end user connects their own account, with API-token auth and no-auth compute Packs also supported.

Distribution is self-serve: a Pack can be private, shared with a team, or published to the Coda Gallery. Selling adds one step — a one-time approval form Coda typically clears within a few days; after approval, no future Pack needs re-approval. Paid Packs are sold as recurring subscriptions, with the maker connecting a Stripe account to receive payouts, and Coda retaining 30% of net proceeds. Choose Coda Packs when your integration's natural home is inside a Coda doc and you want Coda to host the code and handle discovery.

How to build & ship

  1. 1Start a Pack in the browser-based Pack Studio, or run npx packs init locally with the Packs SDK
  2. 2Define building blocks in TypeScript — formulas, sync tables, action formulas, and column formats
  3. 3Add authentication (e.g. OAuth2 or API token) and declare your network domains
  4. 4Build and upload with the packs CLI (or Pack Studio) and test inside a Coda doc
  5. 5Complete the Pack listing page, cut a release with notes, and publish to the Gallery

Key APIs & SDKs

Coda Packs SDK (TypeScript)
packs CLI
Pack Studio (in-browser IDE)
Fetcher / authenticated HTTP
Coda API

Integration types

Connector
Workflow action
Widget

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key, None
  • Security review: Not required
  • Publishing to the Gallery is self-serve; selling requires a one-time approval form (a few days), after which no per-Pack review is needed.
  • Anyone can publish a Pack to the Gallery after completing the listing and releasing a version; there is no heavy per-app certification, though Packs using multiple network domains require Coda approval before upload.
  • Coda enforces API rate limits (429 responses); published Packs are hosted and deployed by Coda.
Auth docs Store policies

Monetization

Free
Paid app
Onboarding
$0 (one-time seller-approval form)
Commission
30% to Coda; the developer receives 70% of net proceeds
Merchant of Record
Developer connects their own Stripe; Coda facilitates the marketplace

Pros & cons for builders

Pros

  • Low barrier — TypeScript, browser-based Studio, and Coda hosts/deploys the Pack
  • Self-service publishing to the Gallery without a lengthy certification gate
  • Clean SDK primitives (sync tables, formulas, actions) for building integrations
  • Native billing/pricing options for Pack makers

Cons

  • Multi-domain network access requires explicit Coda approval
  • Reach is limited to Coda's comparatively smaller user base
  • Execution runs within the Packs sandbox model, constraining some patterns