Review monitoring coverage from Notion and Blazemeter each week
Replace scattered reminders with one weekly view of what is scheduled in Blazemeter and what your active Notion plans expect.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get API Monitoring Schedules
Tool to retrieve a list of all test schedules in your account. use when you need to enumerate existing schedules to manage or review them.
Why this helps
Monitoring coverage can drift across tools, leaving someone to remember when to reconcile the two lists.
- Creates a predictable review rhythm without another reminder to manage.
- Highlights possible gaps between active plans and configured schedules.
- Supports a short, focused weekly cleanup.
Setup
Build it in a few focused steps.
- 1Connect Notion and Blazemeter to Notis once.
- 2Create a scheduled automation in the portal or ask Notis conversationally.
- 3Write one instruction for Notis to compare active Notion monitoring plans with the Blazemeter schedule list and report likely gaps or outdated entries.
- 4Choose a weekly recurring trigger and report channel, then test by running it against current plans and schedules.
Questions about this workflow
Does this change or delete schedules?
No. It retrieves schedules and compares them with active plans for review.
Can the report tell if every plan is covered?
It can identify likely matches and exceptions from the available plan and schedule details; ambiguous entries should be reviewed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Blazemeter. A trigger fires from one place; an action lands in another.
Notion triggers
Blazemeter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Monitoring Schedule
Tool to create a new schedule for running api monitoring tests. use when you need to automate test runs at defined intervals after determining the correct cron expression and test or collection id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Multi Test
Tool to create a new multi-test within a specified project. use after confirming the project id. example: "create a multi-test named 'load-test' in project 12345."
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Project
Tool to create a new project. use when you need to initialize a project in a specific workspace. use after confirming the workspace id.
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.
Create Test
Tool to create a new single test within a specified project. use when registering a new performance test via api.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete API Monitoring Schedule
Tool to delete a specific test schedule by its id. use when you need to remove a scheduled test by its unique schedule identifier.
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 Accounts
Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
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 API Monitoring Schedule
Tool to retrieve details of a specific api monitoring schedule by its id. use when you need to inspect the configuration or timing of an existing schedule.
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 API Monitoring Schedules
Tool to retrieve a list of all test schedules in your account. use when you need to enumerate existing schedules to manage or review them.
Connect any two apps with Notis in the middle.
Notion and Blazemeter, 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 Blazemeter.