How do I connect Notion?

Sign up for Conductor Deck, then add a Notion step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.

Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.

What's the difference between a trigger and an action?

A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.

Notion + Stream Deck

notes · documents · project-management · 8 triggers · 57 actions

Notion centralizes notes, docs, wikis, and tasks in a unified workspace, letting teams build custom workflows for collaboration and knowledge management Add Notion to your Stream Deck workflows with guided setup for the connection details it needs.

Build a Notion workflow — free See how it works

No code
Free tier
Key press or app-event trigger
Pairs with OBS & Elgato tools
OAuth & keys handled in-builder

Templates featuring Notion

Ready-made workflows that use Notion — open one to start in seconds.

Triggers & actions

Events that start your workflow automatically.

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.

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.

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.

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).

Page Created

Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.

Page Properties Updated

Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on data.updated_properties (array of property IDs) to filter downstream.

View Created

Triggers when a new Notion view is created. Fires workspace-wide. The payload includes data.view_type (table, board, gallery, calendar, list, timeline, gantt) and data.parent pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.

About Notion

Notion centralizes notes, docs, wikis, and tasks in a unified workspace, letting teams build custom workflows for collaboration and knowledge management

notesdocumentsproject-management

How to connect

Sign up for free

Create your Conductor Deck account: no credit card required.

Connect Notion

Follow the setup prompts for Notion. Conductor Deck handles the app authorization or required connection details inside the workflow builder.

Build a workflow

Add a Notion action to your visual workflow canvas. Configure the options you need, then connect it to other steps.

Run it from a key, or let events fire it

Sync your workflow to a Stream Deck button, or skip the button: Notion triggers can start it automatically when events happen.

Frequently asked questions

How do I connect Notion?: Sign up for Conductor Deck, then add a Notion step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
Is it free?: Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
What's the difference between a trigger and an action?: A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.