Airtable Marketplace

Productivity

Formagrid, Inc. (Airtable) · Productivity & collaboration suites

Best for: Custom in-base tools and data-driven extensions for Airtable users.

Overview

Airtable Extensions (formerly Blocks) are real-time, interactive apps built with React and the Blocks SDK that run embedded inside an Airtable base. They cover visualizations, internal tools, automations, and integrations with external services, and the marketplace catalogs hundreds of them. Because extensions execute inside the user's base, base-data access needs no separate auth; when an extension talks to an outside service it authenticates there (OAuth 2.0 or API keys), and for server-side automation Airtable's Web API uses personal access tokens or OAuth.

Publishing to the public marketplace is a reviewed step: the developer runs a submit command and provides a name, icon, description, and a declared list of any external services the extension sends data to. Airtable reviews the submission before listing it, and once live the developer owns ongoing maintenance. There is no native billing layer, so extensions are predominantly free with paid functionality gated through the developer's own external service. Choose Airtable Marketplace when your app's value is an interactive, in-base surface sitting directly on a user's tables.

How to build & ship

  1. 1Install the Airtable Blocks CLI and run block init to scaffold an extension
  2. 2Build the UI in React using the Blocks SDK components and hooks against base data
  3. 3Run block run to develop and test live inside a base
  4. 4Release the extension with block release to your base
  5. 5Fill out the marketplace submission form and submit the extension for Airtable's review

Key APIs & SDKs

Airtable Blocks SDK
Blocks CLI (block init/run/release)
React UI component library
Airtable Web API
useRecords / base data hooks

Authentication & security

  • Primary auth: None
  • Also supports: OAuth 2.0, API key
  • Security review: Required
  • Public extensions submit via a CLI review requiring metadata and disclosure of external services and data egress before listing.
  • Extensions submitted for the marketplace go through Airtable's review, checking functionality, quality, security, and listing/design requirements before public publication; no fixed turnaround is published.
  • Web API limited to roughly 5 requests/second per base (429 with a 30s cooldown); in-base extensions run client-side.

Monetization

Onboarding
$0
Commission
No native rev-share; monetization handled outside Airtable
Merchant of Record
Developer handles any billing externally

Pros & cons for builders

Pros

  • React-based SDK and CLI give a productive, modern developer experience
  • Extensions run directly on live base data for powerful in-context tools
  • Local dev loop (block run) makes iteration fast
  • Access to Airtable's substantial base of business users

Cons

  • Marketplace review enforces design/quality/security requirements that can require rework
  • Extensions are scoped to the base context, limiting some cross-app scenarios
  • Smaller marketplace and no rich native monetization compared to major app stores