Skip to content
Notis

Check pipeline configuration when tracking structure changes

A changed Notion schema can cue a quick CircleCI config review when the data source documents build or release operations.

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

Get Pipeline Config

Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.

Why this helps

Structural changes to an operational database can leave related pipeline documentation out of sync.

  • Pairs structural updates with a targeted config lookup.
  • Helps surface stale assumptions in operational documentation.
  • Avoids relying on memory to revisit related pipeline setup.

Setup

Build it in a few focused steps.

  • 1Connect Notion and CircleCI to Notis once in the portal.
  • 2Create an automation prompt that checks whether the changed data source documents a CircleCI pipeline and retrieves its config for review.
  • 3Choose the Notion Data Source Schema Updated trigger for the relevant source.
  • 4Choose a run-report channel and test with a real schema update.

Questions about this workflow

Will every schema change retrieve a config?

Describe in the prompt which data source and kinds of schema changes matter to your workflow.

Does the automation edit the schema or pipeline?

No. It responds with CircleCI configuration for review.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Circleci. A trigger fires from one place; an action lands in another.

Notion triggers

Circleci actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Job Artifacts

Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Job Details

Tool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get Pipeline Config

Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.

ActionInstant

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.

TriggerInstant

Get Test Metadata

Tool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get User Information

Tool to retrieve information about a circleci user by their unique id. use when you need user profile details after obtaining the user id.

ActionInstant

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.

TriggerInstant

List Pipelines for Project

Tool to list all pipelines for a specific project. use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).

ActionInstant

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.

TriggerInstant

List Self-Hosted Runners

Tool to list available self-hosted runners. use when you need to retrieve all configured self-hosted runners for your organization.

ActionInstant

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.

TriggerInstant

List Workflows by Pipeline ID

Tool to list all workflows associated with a specific pipeline. use when you need to fetch or paginate through workflows by pipeline id.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Circleci, 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 Circleci.