Turn a page status change into an indexing check
When you update a page's status, Notis can inspect its URL and report the result without another reminder to yourself.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Inspect URL
Inspects a url for indexing issues and status in google search console.
Why this helps
Finishing a page often creates one more manual step: checking whether search engines can index it.
- Connect a page status update to a practical SEO check.
- See inspection feedback while the work is still fresh.
- Avoid relying on a separate reminder.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Search Console to Notis once in the portal.
- 2Create an automation in the portal or tell Notis to inspect the URL when a page property is updated and report the result.
- 3Select the Notion Page Properties Updated trigger and choose a channel for run reports.
- 4Test by updating a real page that includes its URL.
Questions about this workflow
Can the prompt explain which updates matter?
Yes. Describe in plain language what kind of property update should lead Notis to inspect the page.
Will every property update cause an inspection?
The trigger can fire on property changes. State the intended condition in the automation instruction so Notis can assess the event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google search console. A trigger fires from one place; an action lands in another.
Notion triggers
Google search console actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Sitemap
Retrieves information about a specific sitemap for a site.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Inspect URL
Inspects a url for indexing issues and status in google search console.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Sitemaps
Lists all sitemaps for a site in google search console.
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 Sites
Lists all sites owned by the authenticated user in google search console.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search Analytics Query
Queries google search console for search analytics data including clicks, impressions, ctr, and position metrics.
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.
Submit Sitemap
Submits a sitemap to google search console for indexing.
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 Google search console, 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 Google search console.