Connect Notion and LLMWhisperer to power automations.

Trigger from one app, act on another, with a thinking brain in the middle. Build it in plain English. Approve from your phone.

When this happens · Trigger

Do this · Action

Build an automation Browse templates

Supported Triggers and Actions

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

Notion triggers

LLMWhisperer actions

All Page Events

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

TriggerPolling

Get Usage Information

Tool to check usage metrics of your LLMWhisperer account. Use when you need to monitor API consumption, verify quotas, or check remaining page limits.

ActionInstant

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

Get Usage Statistics

Tool to retrieve usage statistics for your LLMWhisperer account based on a specific tag. Use when you need to check consumption metrics for a given tag and optional date range. Returns usage data for the preceding 30 days when date parameters are omitted.

ActionInstant

New Comment

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

TriggerPolling

Delete Webhook

Tool to delete a registered webhook from LLMWhisperer system. Use when you need to remove a webhook that is no longer needed.

ActionInstant

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

Get Webhook Details

Tool to retrieve registered webhook details for LLMWhisperer. Use when you need to get the configuration of a specific webhook including its URL and authentication token.

ActionInstant

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

Register Webhook

Tool to register a new webhook endpoint for LLMWhisperer async notifications. Use when you need to set up a callback URL to receive processing results. During registration, a test payload is sent to verify the webhook endpoint is functioning and returns HTTP 200.

ActionInstant

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

Update Webhook Configuration

Tool to update an existing webhook configuration for document conversion callbacks. Use when you need to modify the callback URL, authentication token, or webhook identifier. The system validates the webhook by sending a test payload and requires a 200 status response.

ActionInstant

New Page

Triggers when a new page is added to a Notion database.

TriggerPolling

Check Whisper Status

Tool to check the status of a text extraction process in LLMWhisperer. Use when the conversion is done in async mode to poll for completion status.

ActionInstant

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

TriggerPolling

Convert Document to Text

Tool to convert PDFs and scanned documents into LLM-optimized text format asynchronously. Use when you need to extract text from documents for LLM processing. After submission, use the returned whisper_hash to poll status and retrieve converted text. Either document_url (with url_in_post=true) or document_content must be provided.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.