Turn a priority website request into a first test
Add a priority website to your Notion backlog and let Notis start a GTmetrix test, helping move the request toward measurable action.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Start Test
Tool to start a new GTmetrix test for a specified URL. Use when you need to analyze website performance with configurable options like location, browser, and throttling.
Why this helps
Backlog items can remain abstract for too long when the first practical check depends on someone remembering to run it.
- Start a measurable check when a priority request is recorded.
- Reduce delay between identifying a site and reviewing its performance.
- Make progress visible through an automation run report.
Setup
Build it in a few focused steps.
- 1Connect Notion and GTmetrix to Notis once.
- 2Create an automation prompt describing which priority backlog pages should start a test.
- 3Select New Page and scope it to the website backlog data source.
- 4Choose a run report channel and test with one real priority website request.
Questions about this workflow
Will all backlog items start a test?
Describe which requests are priority website checks in the prompt and scope the trigger to the backlog data source.
What does GTmetrix need?
The request should identify the website URL to test; describe where Notis can find it in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to GTmetrix. A trigger fires from one place; an action lands in another.
Notion triggers
GTmetrix actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Page
Tool to delete a specific page in GTmetrix. Use when you need to permanently remove a page resource.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Report
Tool to delete a GTmetrix report. Use when you need to remove an existing performance report from GTmetrix.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Browsers
Tool to retrieve the list of available browsers for GTmetrix performance tests. Use when you need to see which browsers are available and their testing capabilities.
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 Location Details
Tool to retrieve location details from GTmetrix. Use when you need to get information about a specific GTmetrix test location including name, region, browser support, IP addresses, and access permissions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Locations
Tool to retrieve the list of available GTmetrix test locations. Use when you need to see which locations are available for testing and their details including supported browsers and access status.
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.
Get Page Details
Tool to retrieve page details from the user's GTmetrix account. Use when you need to get comprehensive page information including URL, testing configuration, and monitoring frequency.
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.
Get Page Reports
Tool to retrieve the report list associated with a monitored page in GTmetrix. Use when you need to access historical performance data for a specific page. Supports pagination, sorting, and filtering.
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.
Get Pages
Tool to retrieve the page list from your GTmetrix account. Returns a paginated collection of monitored pages with their configurations and latest report information. Use when you need to view all monitored pages, check page configurations, or access latest report data.
Connect any two apps with Notis in the middle.
Notion and GTmetrix, 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 GTmetrix.