Connect Notion to Identitycheck
When something happens in Notion, Notis takes the next step in Identitycheck. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Identitycheck
Review Identitycheck onboardings for each new client
When a client record is added to Notion, retrieve matching Identitycheck onboarding records so you can spot progress without switching tools.
Refresh verification status when a Notion property changes
When a Notion record changes, ask Identitycheck for the latest status of its onboarding and send a concise run report.
Check Identitycheck after verification notes change
When verification notes are edited in Notion, retrieve the associated onboarding status and report it alongside the change.
Look up Identitycheck when a verification case is opened
A new Notion verification case prompts a lookup of related Identitycheck onboarding records, helping you begin follow-up with context.
Look up onboarding records when a verification comment arrives
A new Notion comment can prompt a lookup of related Identitycheck onboardings, so questions arrive with useful context.
Check onboarding status after a question on the verification page
A new comment on a specified verification page prompts a status check for the associated Identitycheck onboarding.
Review Identitycheck configurations after a Notion schema change
When a Notion data source schema changes, fetch Identitycheck configurations for a review report on the workflow records affected.
Review Identitycheck setups when a verification database is created
Creating a Notion database for a new verification process prompts a list of Identitycheck configurations for orientation.
Fetch Identitycheck configurations for a new Notion data source
When a Notion data source is added, retrieve available Identitycheck configurations to help the team orient its verification process.
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
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Identitycheck
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.