Skip to content
Notis

Keep subscription metrics imports moving

Use the page update that reflects new metrics to start a clean handoff of the refreshed dataset.

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

Upload File To Headless Import

Tool to upload a file to a headless import. use after obtaining a signed upload url from dromo. performs an http put of raw bytes to the provided signed url.

Why this helps

Metrics can be updated in one place but remain stale in the import tool until someone remembers the second step.

  • Connects metric updates to the import process.
  • Reduces stale data risk from missed handoffs.
  • Reports when a refreshed dataset is unavailable.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Dromo to Notis once in the portal.
  • 2Create an automation in the portal or ask Notis in plain language.
  • 3Ask Notis in one instruction to upload only the refreshed subscription metrics dataset and report missing files or Dromo prerequisites.
  • 4Choose Notion Page Content Updated for the metrics page and select a report channel.
  • 5Test with one updated metrics dataset.

Questions about this workflow

Will a text correction upload the metrics again?

Tell Notis to require an updated metrics dataset before uploading, and test with a text-only correction.

Can I use a specific metrics page?

Yes, the Page Content Updated trigger can be scoped to a page.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Dromo actions

Recurring trigger

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

TriggerScheduled

List Uploads

Tool to retrieve a list of all uploads stored by dromo for your organization. use when you need to paginate or filter uploads.

ActionInstant

Webhook trigger

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

TriggerInstant

Upload File To Headless Import

Tool to upload a file to a headless import. use after obtaining a signed upload url from dromo. performs an http put of raw bytes to the provided signed url.

ActionInstant

All Page Events

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

TriggerPolling

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

New Comment

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

TriggerPolling

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

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

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

Connect any two apps with Notis in the middle.

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