Connect Agenty to Databricks
When something happens in Agenty, Notis takes the next step in Databricks. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Agenty to Databricks
Turn a website data source into a Databricks connection
Use Agenty to inspect a source website and prepare a Unity Catalog connection request with the details Databricks needs.
Review an external source before using its Databricks connection
Use an incoming request to have Agenty inspect source documentation and retrieve details about the matching Unity Catalog connection.
Update a Databricks connection after a source change
Use Agenty to inspect changed source documentation, then update an existing connection with configuration you have approved.
Check cloud storage details before using a Databricks location
Ask Agenty to inspect cloud storage documentation and retrieve the details of a Unity Catalog external location for review.
Validate a storage credential after checking its provider guidance
Use Agenty to review public provider guidance, then ask Databricks to validate the identified Unity Catalog credential.
Review catalog grants against published access guidance
Use Agenty to inspect access policy pages and retrieve the direct grants on a specified Unity Catalog securable.
Review effective Databricks access against published guidance
Use Agenty to inspect access guidance and retrieve effective Unity Catalog permissions, including inherited access.
Apply an approved catalog permission change
Inspect the relevant access guidance with Agenty, then update Unity Catalog grants using the specific changes you approve.
Update a Databricks app from reviewed release notes
Use Agenty to inspect release or platform documentation, then apply specified configuration updates to an existing Databricks app.
Supported Triggers and Actions
Notis builds workflows that link Agenty to Databricks. A trigger fires from one place; an action lands in another.
Agenty triggers
Databricks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Member to Security Group
Adds a user or group to a Databricks security group.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Custom LLM Agent
Irreversibly deletes a custom LLM agent and all its associated data.
Create Databricks App
Creates a Databricks app in the workspace.
Delete Databricks App
Deletes a Databricks app and its associated service principal.
Deploy Databricks App
Deploys an app from workspace source code and provisions its compute resources.
Get Databricks App Details
Retrieves an app’s configuration, deployment status, resources, and metadata.
Get Databricks App Permission Levels
Lists the permission levels available for an app.
Get Databricks App Permissions
Retrieves who can access an app and their permission levels.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Agenty and Databricks
Connect any two apps with Notis in the middle.
Agenty and Databricks, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Databricks.