Automated Cube Data Model Setup Checklist
Whenever a new data model is added in Cube, WebRun opens Cube Cloud, checks that the model has a description, defined measures and dimensions, and access rules set, saves the checklist result to Google Drive, and texts the owning engineer through Twilio once it's ready to publish or flags what's missing.
How do I make sure every new Cube data model is properly set up before it ships?
Whenever a new data model is added in Cube, WebRun checks it has a description, defined measures and dimensions, and access rules set, saves the checklist result to Google Drive, and texts the owning engineer through Twilio with what's ready or missing. Data platform teams keep every published model documented and access controlled from day one.
- Every new model gets checked before anyone builds on it
- Missing documentation or access rules are caught at publish time, not later
- A dated setup log builds up for every model added
Built for data platform teams · analytics engineers · data governance teams
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
cube.devin a real browser with your saved login - no setup, no API keys. -
1
Cube - check the new model's setup
- Open Cube Cloud and find the newly added data model
- Check it has a description, defined measures and dimensions
- Check access rules are set for the model
Done when The new model's setup checklist is fully checked.
-
2
Google Drive - save the checklist result
drive.google.com
WebRun opens Google Drive to save the checklist result. - Open the data model checklist log in Google Drive
- Save the checklist result with what passed and what's missing
- Keep a dated record for every new model added
Done when The checklist result is saved to the log.
-
3
Twilio - text the owning engineer
twilio.com
WebRun opens Twilio to text the owning engineer. - Message the owning engineer through Twilio
- Confirm the model is ready to publish, or list what's missing
- Name the model in the message
Done when The owning engineer has been texted the checklist result.
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
Does WebRun add the missing description or access rules itself?
No. It only checks whether they're set and reports the gap. Writing a description or setting access rules stays the engineer's task.
Does this run on a schedule or only for new models?
Only when a new data model is added or published in Cube, so it checks fresh models right when they matter, not on a fixed clock.
What if a model is already fully set up?
It still gets logged and the engineer still gets a text, just confirming it's ready to publish rather than listing gaps.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.