← All posts

How updates get triggered in this CMS

How updates get triggered in this CMS This Innerworx demonstration separates editing content from deploying code. Airtable stores the post, Next.js displays it on the Vercel-hosted site, and an automation initiates a refresh when an editor is ready to publish. The publishing decision A post has a slug, title, excerpt, body and status in the Sample CMS base. Editors can prepare and review content without changing the application. The status options are Review, Waiting for Approval, Publish and Published. In this workflow, Publish is the action that starts the automation; Published is a different status. The Airtable trigger The deployed Airtable automation, Update Posts on Website, watches the Posts table for a record matching Status = Publish. Its script takes the triggering record's ID and sends it to a Make webhook as the recordID query parameter. The webhook address is configuration, not something to include in a public article. What Make does next Make receives the hand-off and coordinates the next steps in the publishing workflow. The sample scenario has been tested in production, but its exact modules and mappings are not documented here. A typical implementation looks up the post using its record ID, reads the slug, and calls the site's authenticated revalidation endpoint. That final sequence should be checked against the actual Make scenario before treating it as implementation documentation. Refreshing Next.js The site's POST /api/revalidate endpoint accepts a content type and slug, and requires an x-revalidation-secret header. For a post, the body is {"type":"post","slug":"triggering-updates"}. The endpoint revalidates both the posts listing cache tag and the tag for the individual post. This is why a change can appear on the article page and the posts listing without rebuilding or redeploying the application. The endpoint uses stale-while-revalidate behaviour, so the first request after invalidation may still receive stale content while a refresh is underway. Checking the result After moving a post to Publish, inspect the Airtable automation run, the Make scenario history and the live article. Check both the article URL and the /posts listing. If the change is missing, confirm that the status matched the trigger, the webhook ran, the correct slug was passed and the revalidation request succeeded. A useful distinction The configured Airtable automation watches posts, not pages. Its script sends a webhook but does not itself change a record from Publish to Published. If the Make scenario performs that status update, verify it there. Editing a record that remains Published does not necessarily retrigger the status-based automation; a separate edit trigger or deliberate republishing workflow may be needed. The result is a simple publishing pattern: edit in Airtable, initiate publication with a status change, use Make for integration and let Next.js refresh its cached content. No source-code change is required for routine editorial updates.