Create storage folders for new database entries
When a new project record is inserted into Databricks, automatically create a corresponding project directory in OneDrive.
See all Databricks + OneDrive integrations or talk to a human
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Databricks Explore Databricks →
TriggersFires when a new row is added to a table in Databricks.
Fires when an existing row changes in Databricks.
Fires when a scheduled query in Databricks finishes running.
Runs a SQL query against Databricks and returns the result.
Writes a new or updated row to Databricks.
Syncs a table in Databricks with data from another source.
OneDrive Explore OneDrive →
TriggersFires when a new file is uploaded to OneDrive.
Fires when a file in OneDrive is shared with someone new.
Fires when a folder's contents change in OneDrive.
Uploads a file to OneDrive.
Creates a new folder in OneDrive.
Shares a file from OneDrive with a link or user.
More Databricks + OneDrive workflows
See all Databricks + OneDrive integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create storage folders for new database entries” between Databricks and OneDrive?
Yes — describe it in the box above and Knit's Integrations Agent researches Databricks and OneDrive's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
What's the most common Databases & Warehouses + Files & Storage automation?
Writing file metadata (name, folder, uploader, timestamp) from OneDrive into a table in Databricks as files are added, for audit or usage reporting.
Does this sync the actual file contents, or just metadata?
By default just metadata — the Agent can also extract and sync structured content from a file (like a CSV) into Databricks if that's what you need.