Review storefront context when a Notion process changes
When a Notion data source structure changes, have Notis retrieve the DPD storefront overview as a prompt to review connected operating notes.
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
List Storefronts
Tool to list all storefronts in your dpd account. use after authenticating to fetch storefront details before managing products or purchases.
Why this helps
Structural changes can trigger process reviews, but the related DPD account context is easy to overlook.
- Adds DPD account context to a data source change review.
- Makes it easier to notice storefront details that may affect the updated process.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dpd2 to Notis once in the portal.
- 2Create an automation with a plain-language instruction to retrieve the DPD storefront list when a relevant data source schema changes.
- 3Select the Notion Data Source Schema Updated trigger and choose a channel for run reports.
- 4Test after a suitable schema change and review the storefront reference alongside the process update.
Questions about this workflow
Does this run for a new database?
No. This trigger is for changes to a data source schema, such as a column being added, removed, or renamed.
Does the action edit the Notion schema?
No. The action retrieves DPD storefronts and does not change Notion or DPD data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dpd2. A trigger fires from one place; an action lands in another.
Notion triggers
Dpd2 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Storefront
Tool to retrieve details of a specific storefront by its id. use when you need storefront metadata after you have its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List DPD Customers
Tool to list customers in your dpd account. use when you need a filtered or paginated list of customers for reporting or synchronization.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List DPD Purchases
Tool to list all purchases made through your dpd account. use when you need to retrieve purchase records with optional date filters and pagination for reporting or analysis.
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.
List Storefronts
Tool to list all storefronts in your dpd account. use after authenticating to fetch storefront details before managing products or purchases.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Subscribers
Tool to list subscribers for a given storefront. use when you need a paginated and filtered list of subscribers after storefront setup.
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.
DPD: Ping API
Tool to ping the api to check its status. use when verifying api connectivity before further operations.
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.
Verify DPD Notification
Tool to verify a webhook notification's authenticity by posting back the original signature and payload. use after receiving a notification to confirm it originates from dpd.
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 Dpd2, 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 Dpd2.