Keep presentation checks connected to changing records
When the relevant page changes, Notis can verify its referenced presentation and report what Dock returns.
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
Verify Credential or Presentation
Tool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer.
Why this helps
An updated record can leave teams unsure whether the presentation was rechecked after the change.
- Tie a verification check to the page update that prompted it.
- Make the verification outcome visible in a run report.
- Help teams resume review with a current result.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dock certs to Notis once through the portal.
- 2Create an automation with a plain-language instruction to verify the referenced Dock presentation when the tracked page content changes and report the outcome.
- 3Select Page Content Updated for the relevant page or data source and choose a reporting channel.
- 4Test with one updated page that references a valid presentation.
Questions about this workflow
Does this guarantee a passing verification result?
No. Dock performs the check and returns its result; the team should review that outcome.
Can I scope this to one page?
Yes. Configure the Page Content Updated trigger for the specific page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dock certs. A trigger fires from one place; an action lands in another.
Notion triggers
Dock certs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Key
Tool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete API Key
Tool to delete a specific API key. Use after confirming the API key's ID via list_api_keys.
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.
Delete Credential
Tool to delete a verifiable credential. Use after confirming the credential is no longer needed.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Tag
Tool to delete a specific tag. Use when you have a tag ID and want to permanently remove it.
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.
Delete Webhook
Tool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks.
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.
Retrieve API Key
Tool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering.
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.
Retrieve API Keys
Tool to list all API keys. Use when you need to retrieve all API keys for the authenticated account.
Connect any two apps with Notis in the middle.
Notion and Dock certs, 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 Dock certs.