Automated HashiCorp Run Approval Monitoring
Every hour, WebRun opens HashiCorp Cloud Platform, finds runs whose plan has finished and is waiting on a human to confirm or discard, records the workspace and the waiting time in Airtable, and files a short plan summary in Google Drive for whoever picks it up.
How do I find Terraform runs stuck waiting for approval?
WebRun checks HashiCorp Cloud Platform every hour for runs whose plan has finished and is waiting on a human to confirm or discard. It records the workspace and waiting time in Airtable and files a plan summary in Google Drive, never confirming or applying a run itself.
- A deploy is not blocked all night by an unnoticed confirm
- Every parked run shows the exact hours it has waited
- Repeat blockers surface from a week of history
Built for platform engineers · DevOps teams · SRE teams · infrastructure leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
portal.cloud.hashicorp.comin a real browser with your saved login - no setup, no API keys. -
1
HashiCorp Cloud Platform - find runs awaiting approval
hashicorp.com
WebRun opens HashiCorp Cloud Platform to find runs awaiting approval. - Open HashiCorp Cloud Platform and list runs across your workspaces
- Keep the ones whose plan has completed and is waiting on a confirm or discard
- Note the workspace, the project, who queued the run, and how long it has been parked
Done when Every run awaiting approval is listed with its workspace and waiting time.
-
2
Airtable - track how long each has waited
airtable.com
WebRun opens Airtable to track how long each has waited. - Update a row per parked run with the workspace, project, and hours waiting
- Flag any run parked longer than your threshold, and mark runs now confirmed or discarded as cleared
- Keep the history so repeat blockers show up over the week
Done when Every parked run has a current row with its waiting time.
-
3
Google Drive - file the plan summary
drive.google.com
WebRun opens Google Drive to file the plan summary. - Save a short summary per parked run: workspace, resource changes counted, and any policy check result
- Name the file with the workspace and the run so it is findable later
- Never confirm, apply, or discard a run. WebRun only reports what is waiting
Done when Each parked run has a plan summary filed in Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it confirm or apply a run?
No. Confirming a plan changes real infrastructure, so that always stays with an engineer. WebRun only reports which runs are parked, in which workspace, and for how long.
Does it read the full plan output?
It reads the summary level: the resource change counts and the policy check result. The filed Drive note carries that so an engineer can decide without opening every run.
How often does it check?
Every hour, so a run parked at the end of the day is on the list within the hour rather than sitting untouched until the next morning.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.