Share a Databricks notebook
Databricks solves compute and access control, and both solutions get in the way at the last mile. The analysis is done, the tables are right, and the person who needs to see it — a finance lead, a partner, an exec — does not have a workspace seat and is not getting one for a single number.
So the result gets screenshotted into a deck, which is where analysis goes to lose its context.
Publish the export
From the UI: File → Export → HTML. From a job or a script, use the
workspace export API with format=HTML, then publish the file:
databricks workspace export /Users/me/weekly-revenue \
--format HTML --file weekly.html
curl -fsS -X PATCH \
"https://commareports.com/api/v1/reports/$COMMA_REPORT_ID" \
-H "Authorization: Bearer $COMMA_API_TOKEN" \
-H "Content-Type: application/json" \
-d "$(jq -n --rawfile html weekly.html \
--arg title "Weekly revenue — $(date +%F)" \
'{title: $title, html: $html}')"
One report id per recurring analysis. Each run PATCHes the same URL, so stakeholders bookmark it once and every refresh lands as a revision they can diff against last week.