Case study

Putting an Airtable content calendar on autopilot with Modiva

A look at how lean marketing teams use Modiva with Airtable — publishing every Scheduled record across connected platforms, writing statuses and live URLs back to the base, and bulk-upserting weekly performance rows — without building and maintaining a custom integration.

This is a representative example of the Modiva + Airtable workflow. Have a story to share? Tell us and we’ll feature it here.

The challenge

Teams that live in Airtable rarely want the calendar to stop at the base. Getting records published and results back usually means:

• The whole marketing operation lived in Airtable — calendar, assets, statuses — but publishing was manual, so the base drifted from what was actually live.
• Personal access tokens pasted into scripts were shared far more broadly than anyone intended, with no per-base boundary.
• Performance data never made it back into the base, so the calendar showed what was planned but never what worked.

The approach with Modiva

1. 1

   OAuth scoped to specific bases

   The team authorizes Airtable in Modiva once via OAuth, granting access to specific bases — a per-base grant, not a workspace-wide token. Tokens last about 60 minutes and Modiva refreshes them automatically; access is revocable per base at any time.

2. 2

   Scheduled records become the queue

   An agent lists records where {Status}="Scheduled" through Modiva's typed tools. Copy, assets and target platforms come straight from the record — the calendar in Airtable is the plan that ships.

3. 3

   Publish and write back the live URL

   For each scheduled record, the agent publishes across the team's connected platforms and updates the record to Published with the live URL. The same request shape works across every tool Modiva supports, so adding the next platform is a connection, not a rewrite.

4. 4

   Performance rows upserted weekly

   A weekly job bulk-upserts performance rows into the base — per-post metrics next to the records that produced them — so the calendar shows what worked, not just what was planned.

The outcome

• The base reflects reality without manual updates — statuses, live URLs and performance rows are written back by the agent that published.
• Publishing runs on schedule from the calendar, not from someone's browser tabs at 9am.
• Access is a revocable per-base OAuth grant instead of a personal access token shared across scripts.