A Jotform request moves a contact-page edit through preview and approval
At a glance
A small AI workflow turns a copy-change request into a GitHub branch, a Vercel preview, and a human decision. This workflow is listed under content updates, human approval, deployment.
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Create a Jotform request with the page or file, requested change, definition of done, and risk level. 2) In n8n, connect a Jotform trigger and a model node; map the form fields into the prompt and have the planner return one content file, a branch name, and a summary. 3) Fetch that file from GitHub, have Claude make only the requested content change, and write the result to the planned branch. 4) Connect the repository to Vercel so the branch gets a preview URL. Send that URL to a second Jotform approval form, inspect it, and approve or reject the change; Vercel deploys the live version after an approved merge. 5) Add a scheduled GitHub check that requests the live site and fails if it is unavailable.
Worth knowing
The article demonstrates the workflow with contact-page copy. Its approval step is manual and the live deployment follows a GitHub merge.
