STEP 1
Connect Databricks and Microsoft Files
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Databricks and Microsoft Files Integration
Build developer tools workflows between Databricks and Microsoft Files on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Databricks and Microsoft Files
Detailed info you need to know about Databricks and Microsoft Files integrations in WEXTL. Explore which modules apps support and how you connect them.
Databricks
Run Databricks jobs, clusters, SQL, files, Unity Catalog, and model serving from a workspace. [5]
Microsoft Files
OneDrive and SharePoint files — upload, download, and manage documents. [6]
How to connect Databricks to Microsoft Files
Set up your Databricks and Microsoft Files integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Databricks and Microsoft Files nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Databricks and Microsoft Files. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Databricks and Microsoft Files work in WEXTL?
WEXTL exposes actions and triggers for Databricks and Microsoft Files that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Databricks triggersMicrosoft Files actions
Databricks modules
- Cancel All RunsCancels all runs of a job.
- Cancel RunCancels a job run.
- Cancel SQL StatementCancels a SQL statement.
- Change Cluster OwnerChanges the owner of a cluster.
- Create CatalogCreates a catalog.
- Create ClusterCreates a new cluster.
- Create Conversation MessageSends a message in a Genie conversation.
- Create DirectoryCreates a volume directory.
- Create FunctionCreates a function.
- Create JobCreates a new job.
- Create RepoCreates a new repo.
- Create SchemaCreates a schema.
- Create Secret ScopeCreates a secret scope.
- Create Serving EndpointCreates a serving endpoint.
- Create SQL WarehouseCreates a SQL warehouse.
- Create Vector Search IndexCreates a vector search index.
- Create VolumeCreates a volume.
- Create Workspace DirectoryCreates a workspace directory.
- Delete CatalogDeletes a catalog.
- Delete Cluster PermanentlyPermanently deletes a cluster.
- Delete DirectoryDeletes an empty volume directory.
- Delete FileDeletes a file from a Unity Catalog volume.
- Delete FunctionDeletes a function.
- Delete JobDeletes a job.
- Delete RepoDeletes a repo.
- Delete RunDeletes a job run.
- Delete SchemaDeletes a schema.
- Delete SecretDeletes a secret.
- Delete Secret ACLDeletes a secret ACL.
- Delete Secret ScopeDeletes a secret scope.
- Delete Serving EndpointDeletes a serving endpoint.
- Delete SQL WarehouseDeletes a SQL warehouse.
- Delete VolumeDeletes a volume.
- Delete Workspace ObjectDeletes a workspace object.
- Download FileDownloads a file from a Unity Catalog volume.
- Edit ClusterEdits an existing cluster.
- Edit SQL WarehouseEdits a SQL warehouse.
- Execute Message SQL QueryExecutes the SQL query on a Genie message attachment.
- Execute SQL StatementExecutes a SQL statement on a warehouse.
- Export RunExports a job run.
- Export Workspace ObjectExports a workspace object.
- Get CatalogReturns a catalog.
- Get ClusterReturns a single cluster.
- Get Conversation MessageReturns a Genie conversation message.
- Get File MetadataReturns metadata for a volume file.
- Get FunctionReturns a function.
- Get Genie SpaceReturns a Genie space.
- Get JobReturns a single job.
- Get Job RunReturns a single job run.
- Get Job Run OutputReturns output for a job run.
Microsoft Files modules
- Activeate a File Container StorageActivate a file storage container object.
- Add Bundle ItemAdd an additional driveItem from a drive to a bundle.
- Copy a Drive ItemMake a new copy of a drive item.
- Create a BundleAdd a new bundle to the user's drive.
- Create a File Container StorageCreate a new file storage container object.
- Create a File Container Storage TypeCreate a new file storage container type.
- Create a FolderCreate a new folder in a drive.
- Delete a BundleRemove a bundle by a provided ID.
- Delete a Bundle ItemRemove an item from a bundle.
- Delete a Drive ItemDelete a DriveItem by using its ID or path.
- Delete a File Container StorageRemove a file storage container object.
- Delete a File Container Storage TypeRemove a single storage container type.
- Download a FileDownload the contents of the primary stream (file) of a drive item.
- Follow a Drive ItemPerforms the a Drive Item operation.
- List Available DrivesRetrieve the list of Drive resources available for a target User, Group, or Site.
- List BundlesGet a list of all the bundles in a user's drive.
- List Drive ActivitiesList the recent activities that took place on a drive.
- List File Storage ContainerGet a list of fileStorageContainer objects that are accessible to a caller.
- List File Storage Container TypesGet a list of the file storage container type objects and their properties.
- List Followed ItemsList the items that have been followed by the signed in user.
- Make an API CallPerform an arbitrary authorized API request.
- Move a Drive ItemMove a driveItem to a new folder.
- Remove a Deleted File Container StoragePermanently remove a deleted file storage container object.
- Restore a Deleted File Container StorageRestore a deleted file storage container object.
- Retrieve a BundleRequest a single bundle by a provided ID.
- Retrieve a DriveRetrieve the properties and relationships of a Drive resource.
- Retrieve a Drive ItemRetrieve the metadata for a driveItem in a drive by file system path or ID.
- Retrieve a File Container StorageRetrieve the properties of a file storage container object.
- Retrieve a File Container Storage TypeRequest a single storage container type.
- Retrieve User DriveRetrieve the properties and relationships of a Drive resource for the current authenticated user.
- Update a BundleUpdate the metadata for a bundle of driveItems by ID.
- Update a FileUpdating an existing file.
- Update a File Container StorageUpdate the properties of a file storage container object.
- Update a File Container Storage TypeUpdate the properties storage container type.
- Upload a FileUpload a new file.
- Watch DrivesTriggers when new drives are created.
- Watch File Storage ContainerWatch for new file storage container.
- Watch File Storage Container TypeWatch for new file storage container type.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Databricks and Microsoft Files integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Databricks and Microsoft Files.
Connect your Databricks and Microsoft Files accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Databricks's "Watch Job Runs" fires, WEXTL can "Activeate a File Container Storage" in Microsoft Files. Databricks has 1 trigger (including Watch Job Runs); Microsoft Files has 35 actions (including Activeate a File Container Storage, Add Bundle Item, and Copy a Drive Item). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Databricks-to-Microsoft Files automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Databricks (or Microsoft Files) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Databricks + Microsoft Files automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Databricks and Microsoft Files integration.
- Databricks and Microsoft Files integration source code, module specs and credentials implementation.
- Our Databricks and Microsoft Files integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Databricks and Microsoft Files — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Databricks integration information
- Microsoft Files integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library