OpenRows docs
How to use OpenRows, run your own instance, move from Airtable and build on the API.
Get started
User guide
- Bases, tables and recordsHow to organize data in bases and tables, edit records in the grid, comment, follow a record's history, import, export, restore and snapshot.
- FieldsEvery field type in OpenRows, its options, how type conversions work, links, lookups and rollups, formulas and their functions, and per-field edit permissions.
- ViewsA view is one way of looking at a table: a grid, a board, a calendar, cards, a timeline, a nested list or a form, each with its own filters, sorts and layout.
- Sharing and permissionsInvite people to a workspace or a single base, choose their role, narrow who can edit a table or field, and share read-only links to views and bases.
- FormsA form view turns a table into a public form. Anyone with the link can fill it in, and each submission adds a record to the table.
- AutomationsAutomations run actions when something happens in a base: create or update records, send emails, Slack messages or HTTP requests, or run a script.
- ScriptsScripts are small JavaScript programs that work on a base: clean up duplicates, change many records at once or build a report. They run in your browser, in a sandbox, with your own permissions: a…
- ExtensionsExtensions are small apps that sit next to your views in a base's extension panel: a chart that updates as records change, a print layout of the record you've selected, a preview of a record's link…
Guides
- Moving from AirtableBring your Airtable bases into OpenRows with the built-in importer, see what changes on the way, and point code written for Airtable's API at OpenRows.
- Self-hostingRun your own OpenRows server with Docker Compose or on Kubernetes with the Helm chart: the image, the services, the settings production requires, sign-in, storage, email, backups and upgrades.
- Audit logOn the hosted service's Enterprise plan, every workspace keeps an audit log: who did what, when and from where. Owners open it from the workspace menu (Audit log). Self-hosted OpenRows doesn't keep…
- Single sign-onOn the hosted service's Business and Enterprise plans, a workspace can let its people sign in with your organization's identity provider: anything that speaks SAML 2.0 or OpenID Connect, such as…
- SCIM provisioningOn the hosted service's Business and Enterprise plans, your identity provider can manage who is in a workspace with SCIM 2.0: Okta, Microsoft Entra ID, OneLogin, JumpCloud and anything else that…
- Admin console and workspace policiesOn the hosted service's Enterprise plan, a workspace's owners have an Admin console: open the workspace menu and select Admin console. It shows the workspace's policies, its single sign-on and SCIM…
- ZapierThe OpenRows app for Zapier connects your bases to the thousands of apps Zapier works with: start a Zap when a record is added or changed, and create, update, find or delete records from any other…
- MakeThe OpenRows app for Make connects your bases to the apps Make works with: start a scenario when a record is added or changed, and create, update, get, search or delete records from any other app.
Developers
- REST API v1OpenRows' public, versioned API follows the shape of Airtable's Web API, so integrations and scripts written for Airtable work with few changes. It lives under /api/v1 and is described, with every…
- API referenceEvery operation of the REST API and the app API, generated from the OpenAPI document.
- WebhooksOpenRows sends a base's changes to a URL you choose, as signed JSON. Use them to push records into n8n, Zapier, Make or your own code instead of polling the REST API.
- OAuth appsIntegrations that act for other people (a Zapier or Make app, a SaaS connector) register an OAuth app instead of asking each person for a personal access token. OpenRows is the authorization server…
- MCP serverAI agents use OpenRows through the Model Context Protocol, two ways, with the same tools:
- @openrows/sdkA typed JavaScript client for the OpenRows REST API v1. ESM and CommonJS, Node 20+ and browsers, no dependencies beyond fetch. Its types are generated from the API's own contracts, so they say what…
For AI assistants: llms.txt and llms-full.txt hold these docs as Markdown.