Airtable integration
Airtable is on the map, not in the product yet.
A two-way content calendar: planned topics flow in from your base, status and performance flow back.
How it works
Airtable connects through OAuth, scoped to the specific base you grant, which is the path Airtable itself prescribes for third-party integrations; Airtable is explicit that personal access tokens should not be handed to outside services. Once connected, the integration works both directions: we read planned topics from your content calendar base, and we write back status, live URLs, and performance as pieces move through the pipeline.
In the loop, Airtable can steer the opportunity and write steps and receive the publish and measure steps. Topics your team plans in the base become inputs to what gets written, and the same rows fill in with what happened: published, indexed, and how the page performs. The base stays the single place your team looks.
Best forTeams who plan content in an Airtable base and want it to drive the pipeline and receive results in place.
Setup, step by step
- Click Connect on the Airtable card, which starts Airtable's OAuth flow.
- Grant access to the specific base holding your content calendar.
- The connector runs a dry-run read to verify the base grant actually covers the tables we need.
- Map your fields once: topic, status, URL, and the performance columns you want filled.
- Run the first sync and confirm both directions land in the right fields.
Best practices
Grant the one base, not everything
Airtable's OAuth lets you scope access to a single base, and that is the right grant. The integration needs your content calendar, not your whole workspace, and the narrow grant proves it.
Treat mapped fields as an interface
Renaming or retyping a mapped field changes what sync reads and writes. When the base evolves, revisit the mapping in the connector so the two sides stay aligned.
Plan in your own fields freely
We only touch the fields you map. Notes, owners, review columns, and any views your team builds live alongside untouched, so the base remains a planning tool first.
Work with the batch rhythm
Sync runs on a schedule rather than on every cell edit. Plan and edit at your pace; changes flow on the next sync, and a manual sync button covers the moments you cannot wait.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Personal access tokens are the wrong tool here
Airtable states plainly that personal access tokens are for a user's own scripts and should not be given to third-party services, so token-based connectors are off-spec by design.
How we handle itWe built on OAuth only, the path Airtable prescribes for integrations, so there is never a personal token of yours in our hands and revoking access is a standard OAuth revoke.
airtable.com
Access is limited to the granted bases and scopes
The connection can only see the bases and scopes granted in the OAuth flow, so a grant that misses the calendar base leaves the integration connected but unable to read anything useful.
How we handle itThe connect flow verifies the grant with a dry-run read of your calendar base before finishing, so a wrong or incomplete grant is caught at setup, not discovered as a silent empty sync.
airtable.com
Questions teams ask
- Can SearchHandled see our other bases?
No. Airtable's OAuth scopes the connection to the bases you grant, and we ask for the one holding your content calendar. Everything else in your workspace is invisible to us by design.
- What happens if two people edit the same row the sync touches?
Your edits to unmapped fields are never touched. For mapped fields, the pipeline writes its own facts, status, URL, and performance, and treats topic and planning fields as yours to edit.
- What if we do not use Airtable?
CSV import and export cover the same calendar data manually, and the Google Sheets integration offers a similar two-way flow for spreadsheet-based teams.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Airtable matters moves it up the rollout.