Connect Notion to Datarobot
When something happens in Notion, Notis takes the next step in Datarobot. 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 Notion to Datarobot
Analyze new dataset briefs
When a dataset brief is added to Notion, ask DataRobot to inspect the referenced dataset definition for schema, metadata, and statistics.
Request review for deployment changes
Use a change in a Notion governance or release record to create a DataRobot deployment change request for authorized review.
Carry model feedback into DataRobot
When a Notion page with model feedback changes, add a comment to the relevant DataRobot entity to keep the discussion near the work.
Document dataset schema changes
When a Notion data source schema changes, request a DataRobot automated compliance document for the related project, model, or deployment.
Start a DataRobot custom job from a plan
When a new Notion page describes a planned repeatable execution task, create a named DataRobot custom job for the work.
Ingest a file referenced by a new data record
When a new Notion data intake record points to an accessible file, create a DataRobot catalog dataset from that file.
Prepare a holiday calendar for modeling
When a Notion planning view is created, initialize a DataRobot holiday calendar for a relevant country and date range.
Define batch prediction runs from plans
When a Notion scoring plan is edited, create a reusable DataRobot batch prediction job definition for that planned workload.
Add monitoring to planned batch scoring
When a Notion batch scoring record is updated, start a DataRobot batch monitoring job for the corresponding deployment.
Supported Triggers and Actions
Notis builds workflows that link Notion to Datarobot. A trigger fires from one place; an action lands in another.
Notion triggers
Datarobot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Users to Group
Tool to add one or more users to a DataRobot user group by groupId. Use when you have a valid groupId and want to add existing usernames. Limit 100 users per request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User to Organization
Tool to add a user to an existing organization. Use when you have an organizationId and wish to add or create a user within it.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Analyze Dataset Definition
Tool to analyze a dataset definition by ID. Use when you need to trigger an analysis job that retrieves dataset metadata, schema, and statistics.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Archive Model Package
Tool to archive a DataRobot model package. Use when you need to archive a model package that is no longer actively used.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Build Java Scoring Code Package
Initiates an asynchronous build of a Java JAR package containing DataRobot Scoring Code for a deployment. The JAR can be executed locally for predictions or used as a library in Java applications. Use after confirming the deployment is active and supports scoring code. Poll the returned statusId or location URL to track build progress.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Cancel Notebook Job
Tool to cancel a running or pending notebook job execution. Use when you need to stop a notebook job that is currently executing or queued. The cancellation is immediate and cannot be undone.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Cancel Project Job
Tool to cancel a pending job for a project. Use when you need to stop a queued or running job after confirming its ID.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Check Project Status
Tool to check the status of a DataRobot project. Use after creating or loading a project to monitor its stage and Autopilot completion.
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 Notion and Datarobot
Connect any two apps with Notis in the middle.
Notion and Datarobot, 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 Datarobot.