Skip to content
Notis

Validate a Blazemeter test from its Notion brief

Use the readiness change your team already records to prompt a validation check and bring the result back into view.

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

Validate Test

Tool to validate a specific test by its id. use after creating or updating a test to ensure its configuration is valid.

Why this helps

A test can be marked ready in a planning database while validation remains an easy-to-miss separate step.

  • Puts validation next to the readiness signal in the workflow.
  • Surfaces configuration issues soon after the team marks a brief ready.
  • Provides a run report that helps the owner take the next step.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Blazemeter to Notis once in the portal.
  • 2Create an automation by asking Notis or using Automations in the portal.
  • 3Write one instruction asking Notis to validate the referenced Blazemeter test when a Notion brief is marked ready, and report the outcome.
  • 4Select Page Properties Updated as the trigger, choose where reports should go, and test with one ready brief.

Questions about this workflow

Will every property edit cause validation?

The event fires on property updates. State in the plain-language instruction that validation is only for briefs marked ready, and test that behavior with a real item.

Does validation execute the test?

No. It checks the test configuration through Blazemeter's validation action.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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."

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

Create Test

Tool to create a new single test within a specified project. use when registering a new performance test via api.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

Get Accounts

Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.