Automating publishing with Airtable and Make
Automating publishing with Airtable and Make
This Innerworx sample demonstrates a simple division of responsibilities: Airtable is the content management system, an Airtable automation detects a publishing decision, Make coordinates the integration, and Next.js renders the website on Vercel. The goal is to publish an editorial change without touching the source code or running a new deployment.
1. Manage the content in Airtable
The Posts table holds the slug, title, excerpt, content, author, published date and status. The slug is the URL-friendly identifier used by the website. Editors prepare the content in Airtable and use Status to move it through the workflow. The current choices are Review, Waiting for Approval, Publish and Published.
2. Use Publish as the trigger
The deployed Airtable automation is called Update Posts on Website. Its trigger matches a Posts record when Status equals Publish. This is an important distinction: Publish initiates the workflow, whereas Published is a separate status. Simply editing a record already marked Published does not, by itself, meet this automation's Publish condition.
3. Hand the record to Make
The Airtable automation runs a script that reads the triggering record ID and calls a Make webhook with that ID in the recordID query parameter. The record ID is a stable way to identify the item even if its title changes. Keep webhook URLs and credentials in configuration rather than exposing them in published content.
4. Resolve the content and refresh the website
The intended Make-side flow is to receive the record ID, look up the corresponding post in Airtable, obtain its slug, and send a POST request to the website's /api/revalidate endpoint. That endpoint expects a JSON body containing type = post and the slug, plus an x-revalidation-secret header. It invalidates the posts collection and the specific post cache tags. The Next.js endpoint is present in the application's repository; the precise Make module sequence and field mappings have not been independently inspected for this article.
5. Check the result
Review the Airtable automation run and Make scenario history, then visit both the individual article and the /posts listing. A successful revalidation response reports the tags that were invalidated. Because the application uses stale-while-revalidate caching, allow for a subsequent request to refresh content rather than expecting an instantaneous change for every visitor.
6. Handle editorial status deliberately
If your Make scenario moves a successful item from Publish to Published, confirm that behaviour in the scenario and test it. The Airtable automation itself currently sends the webhook; its script does not update the status. Avoid claiming the entire publishing workflow is complete based only on a webhook request: inspect failures and confirm the live page.
Why this pattern is useful
Editors work in a familiar table, integration logic is kept separate from the website, and Next.js can cache content for efficient delivery. The same revalidation endpoint also accepts type = page, but the Airtable automation described here watches the Posts table only; page publishing would require its own trigger or another integration path.
Try it yourself: prepare a test post, change its status to Publish, inspect the automation and Make run, and verify the result on the live website. This demonstration focuses on the architecture and workflow, not on publishing private webhook addresses or credentials.