Connect Databricks to monday.com
We build integrations that let monday.com drive Databricks: a change on a board runs an action in Databricks.
What monday.com can do in Databricks
Actions a change on a board can run in Databricks.
| Action |
|---|
| Files |
| File: Create directory |
| File: Delete directory |
| Delete file |
| Download file |
| Get file metadata |
| File: List directory |
| Upload file |
| Genie |
| Genie: Create conversation message |
| Genie: Execute message SQL query |
| Genie: Get conversation message |
| Get genie space |
| Genie: Get query results |
| Genie: Start conversation |
| Unity catalog |
| Create catalog |
| Unity catalog: Create function |
| Unity catalog: Create table |
| Unity catalog: Create volume |
| Delete catalog |
| Unity catalog: Delete function |
| Unity catalog: Delete table |
| Unity catalog: Delete volume |
| Get catalog |
| Unity catalog: Get function |
| Unity catalog: Get table |
| Unity catalog: Get volume |
| Unity catalog: List catalogs |
| Unity catalog: List functions |
| Unity catalog: List tables |
| Unity catalog: List volumes |
| Update catalog |
| Databricks SQL |
| Databricks SQL: Execute query |
| Model serving |
| Model serving: Query endpoint |
| Vector search |
| Vector search: Create index |
| Vector search: Get index |
| Vector search: List indexes |
| Vector search: Query index |
Recipes
Each recipe is one change and what it does on the other side.
When an item's status changes in monday.com, run "File: Create directory" in Databricks.
Keep Databricks as it is. We connect it to monday.com.
We build the integration around what you already have. Databricks keeps doing the job it does for you today, and monday.com gets the data it needs to plan and track the work around it.
Before we build, we agree which system owns each record. The integration then carries data between Databricks and monday.com, so nobody copies it by hand.
Nothing your team relies on has to be replaced.
We highly recommend Worktables. They took the time to listen to all of our challenges and created an integrated system to manage all aspects of our operations.
What stays the same
Databricks stays as it is
The integration connects to Databricks the way you use it today. It moves the data, and nothing you rely on has to change.
Each record lives once
We agree which system owns each record before we build, so there is one right copy, not two.
Data arrives on its own
When data needs to reach the other side, the integration carries it. No exports, no re-keying.
How we connect Databricks to monday.com
-
Scope
We agree which system owns each record, which events should move it, and which board it lands on.
-
Build the workflow
We build the workflow that carries data between Databricks and monday.com and logs every run.
-
Connect the board
We map each field to your columns, groups and statuses, and test on a copy of the board before it goes live.
-
Support
We watch it after launch, fix what breaks, and change it when your process changes.
Questions about connecting Databricks
Do we have to replace anything?
No. Databricks stays as it is, and so does monday.com. The integration carries data between them; it does not replace either one.
What if monday.com already offers an integration with Databricks?
Then we start from what it covers. Where it does the job, we build on it; where your process needs more, we build around it.
Can we test it before it goes live?
Yes. We test on a copy of your board before the integration touches the live one.
Who looks after it once it is running?
We do. We watch it after launch, fix what breaks, and change it when your process changes. Every run is logged, so there is a record of what moved and when.
Related in Databases & Storage
See more in Databases & StorageTell us what Databricks and monday.com should do together
Book a free call and walk us through your process. We'll tell you what the integration should do and how we'd build it.