Keep data source setup moving after schema changes
A schema update can prompt connector setup in BigML, so the next analysis step is easier to pick up.
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 External Connector
Tool to create a new external connector for data sources. use after configuring external databases or search indices.
Why this helps
Structural changes are easy to forget when they require a separate trip into another tool.
- Bring connector setup into the same workflow as schema maintenance.
- Reduce the chance that an updated source is overlooked.
- Make follow-up setup visible through Notis run reports.
Setup
Build it in a few focused steps.
- 1Connect Notion and BigML to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one plain-language instruction, ask Notis to create the appropriate BigML external connector when the relevant source schema changes.
- 4Select the Notion Data Source Schema Updated trigger, then choose a channel for run reports.
- 5Test with a real schema update and check the connector created in BigML.
Questions about this workflow
Does the trigger run for every data source?
It can fire workspace-wide or be scoped to a single data source when configuring the trigger.
What does the BigML action create?
It creates an external connector. The instruction should explain the intended source context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bigml. A trigger fires from one place; an action lands in another.
Notion triggers
Bigml actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create External Connector
Tool to create a new external connector for data sources. use after configuring external databases or search indices.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new project. use when you need to group related bigml resources into a project.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Project
Tool to delete an existing project. use when you need to permanently remove a project resource after confirming it is not in use by other resources.
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.
Get External Connector
Tool to retrieve details of an external connector. use after creating or listing external connectors to inspect its state.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Project
Tool to retrieve details of a project by id. use when you need to inspect project metadata before analysis.
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.
List Correlations
Tool to list correlation resources. use when you need to browse or paginate existing correlations for the authenticated user.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Bigml, 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 Bigml.