Start verification when the fix is ready
Document the fix in Notion and let that update start the CircleCI run, keeping verification connected to the work that prompted it.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Trigger Pipeline
Tool to trigger a new pipeline for the specified project. use when you need to start a build on a branch or tag programmatically.
Why this helps
A fix can be documented and ready while the verification build waits on someone to remember to trigger it.
- Starts verification from a meaningful engineering update.
- Links the build run to the page describing the fix.
- Reduces the chance of forgetting the follow-up build.
Setup
Build it in a few focused steps.
- 1Connect Notion and CircleCI to Notis once in the portal.
- 2Create an automation prompt that starts the appropriate CircleCI pipeline when a scoped fix page is updated and marked ready.
- 3Choose the Notion Page Content Updated trigger for the relevant page or data source.
- 4Choose a run-report channel and test with one real approved fix update.
Questions about this workflow
Can every page edit trigger a build?
Describe the conditions that indicate the fix is ready in the prompt and scope the trigger to the relevant page or source.
Can the pipeline run on a specific branch?
Include the intended project and branch in the plain-language automation instruction.
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.
Get Job Artifacts
Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
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 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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 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).
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.
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.
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.
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.
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.