Check the credential catalog from a new review view
Build a useful catalog lookup into the moment a credential review view is introduced.
Trigger
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.
Action
List Credentials
Tool to list credentials. use after authentication to retrieve paginated credentials.
Why this helps
Creating a new review view can be followed by manual searches to populate the context needed for the review.
- Pair a review workflow with a credential list lookup.
- Reduce the extra step of opening Certifier just to begin discovery.
- Make the new view more useful from the start.
Setup
Build it in a few focused steps.
- 1Connect Notion and Certifier to Notis once.
- 2Create an automation asking Notis to list Certifier credentials when a new credential review view is created.
- 3Select the Notion View Created trigger and instruct Notis to act only for relevant review views.
- 4Choose where run reports go and test by creating a credential review view.
Questions about this workflow
Does this apply to every Notion view?
Tell Notis to act only when the new view is for credential review.
Does listing credentials change them?
No. The Certifier action retrieves the credential list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Certifier. A trigger fires from one place; an action lands in another.
Notion triggers
Certifier actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Send a Credential
Tool to send a published credential via email. use after confirming the credential is published.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create, issue, and send credential
Tool to create, issue, and send a credential in a single request. use when group id and recipient details are ready.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Credential Interactions
Tool to list credential interactions. use when you need to retrieve interaction events for a specific credential, with optional filtering and pagination.
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 Credentials
Tool to list credentials. use after authentication to retrieve paginated credentials.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Designs
Tool to list all designs. use after authentication to retrieve certificate and badge designs with pagination.
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 Groups
Tool to list all groups. use when you need to retrieve groups with pagination (limit and cursor).
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.
Connect any two apps with Notis in the middle.
Notion and Certifier, 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 Certifier.