Check async extraction from a Notion page
Use a page update to check the progress of the document extraction connected to that page.
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
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.
Why this helps
Remembering to poll an async process competes with the work the extracted document is meant to support.
- Attach progress checks to a page that already matters.
- Cut down on manual polling.
- Make pending document work easier to revisit.
Setup
Build it in a few focused steps.
- 1Connect Notion and LLMWhisperer to Notis once.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Give Notis one instruction to check the status of the extraction job associated with the updated page.
- 4Choose the Notion Page Content Updated trigger for the relevant page and select a reporting channel.
- 5Test with an active async job associated with that page.
Questions about this workflow
Will this retrieve text when the job completes?
This workflow checks status only. Text retrieval requires a separate action after completion.
What must the page provide?
The correct whisper hash must be available to Notis when it checks the job.
When this happens · Trigger
Do this · Action
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Webhook
Tool to delete a registered webhook from LLMWhisperer system. Use when you need to remove a webhook that is no longer needed.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and LLMWhisperer, 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 LLMWhisperer.