Document modeling changes from Notion schema updates
A changed data structure can affect downstream modeling. Let a tracked Notion schema update prompt documentation generation in DataRobot.
Trigger
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.
Action
Create Automated Document
Tool to request generation of automated compliance documents in DataRobot. Use when you need to generate documentation for projects, models, or deployments. The document generation is asynchronous. Poll the returned location URL to check status and retrieve the document once generation completes.
Why this helps
Structural data changes can be easy to overlook when documentation happens in a separate system.
- Connects a schema change signal to documentation follow-through.
- Helps keep project or model records current as source structure evolves.
- Avoids relying on memory to start a separate document request.
Setup
Build it in a few focused steps.
- 1Connect Notion and DataRobot to Notis once in the portal.
- 2Create an automation instructing Notis in plain language to request a compliance document for the related DataRobot asset after a schema change.
- 3Select Notion Data Source Schema Updated as the trigger and pick a reporting channel.
- 4Test with one real schema change and a clearly identified DataRobot asset.
Questions about this workflow
What does DataRobot generate?
It requests an automated compliance document for a project, model, or deployment.
Is the document returned immediately?
Document generation is asynchronous; the workflow requests generation and DataRobot processes it afterward.
When this happens · Trigger
Do this · Action
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.
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.