Keep your Search Console site inventory visible
Update a site note and have Notis list the properties available in Search Console, helping you spot which site is ready for a check.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
List Sites
Lists all sites owned by the authenticated user in google search console.
Why this helps
When managing more than one web property, finding the right Search Console site can add avoidable friction.
- Surface the connected account's site list in a familiar workflow.
- Reduce uncertainty about which properties are available.
- Make multi-site checks quicker to start.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Search Console to Notis once in the portal.
- 2Create an automation asking Notis to list Search Console sites when the relevant site note changes.
- 3Select All Page Events and choose a channel for run reports.
- 4Test by updating one real site note and reviewing the property list.
Questions about this workflow
Does this add a site to Search Console?
No. It lists the sites already available to the authenticated account.
When is this useful?
It can help when organizing work across several properties or confirming which properties the connected account can access.
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.