Bring a requested verification document into a focused review
When a review page is created, Notis can retrieve the specified Identitycheck document content for the intended review.
Trigger
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.
Action
Get Document Content
Tool to retrieve base64-encoded document content. Use when you have an onboarding UID and document code.
Why this helps
Finding a document for a review can interrupt focused work and add another manual retrieval step.
- Reduce steps between opening a review and retrieving its document.
- Keep the retrieval request connected to the review context.
- Make document lookup a deliberate part of the review workflow.
Setup
Build it in a few focused steps.
- 1Connect Notion and Identitycheck to Notis once in the portal.
- 2Create an automation that retrieves the specified Identitycheck document when a review page is created.
- 3In plain language, describe how Notis should identify the onboarding UID and document code and report the result securely.
- 4Select Page Created for the appropriate review data source and choose a suitable report channel.
- 5Test with one authorized real example and confirm the retrieved content is handled appropriately.
Questions about this workflow
What does this action return?
It retrieves base64-encoded document content for a specified onboarding UID and document code.
Should every review page trigger document retrieval?
Use a narrowly scoped Page Created trigger and only retrieve a document when the review requires it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Identitycheck. A trigger fires from one place; an action lands in another.
Notion triggers
Identitycheck actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check API Health
Tool to perform API health check. Use to verify API availability before other operations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete configuration
Tool to delete an existing configuration. Use when you need to remove a configuration by its unique code.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Notification Endpoint
Tool to delete a notification endpoint. Use after confirming the endpoint code exists and you need to remove it.
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.
Fetch All Configurations
Tool to fetch all existing configurations. Use when you need to list all customer configurations after authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Fetch all notification endpoints
Tool to fetch all notification endpoints. Use when you need to list all existing notification endpoints.
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.
Fetch Configuration
Tool to fetch a configuration by its code. Use when you need detailed settings of a specific identity check configuration.
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.
Fetch Notification Endpoint
Tool to fetch a notification endpoint by its code. Use when you need the current configuration of a specific callback endpoint.
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.
Fetch Onboardings
Tool to retrieve onboardings. Use when you need to list onboardings with filters like UID, status, date range, etc. Example: List onboardings created since 2023-01-01 with status SUCCESS
Connect any two apps with Notis in the middle.
Notion and Identitycheck, 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 Identitycheck.