Skip to content
Notis

Stop Blazemeter load tests when a GitHub workflow fails

A failed build should not leave a performance test running unattended. Have Notis stop the relevant Blazemeter master and report the result.

Trigger

GitHub Workflow Run State Changed

Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).

Action

Stop Master

Tool to stop a specific test execution (master) by its id. use when you need to abort a running test.

Why this helps

When a build fails, finding and stopping its associated performance run adds another manual follow-up.

  • Reduce wasted test runtime after a failed build.
  • Keep failure handling visible in one run report.
  • Use the workflow run outcome to decide when to stop a test.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Blazemeter once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
  • 3In one instruction, say which Blazemeter master to stop when the monitored GitHub workflow run concludes with failure.
  • 4Pick GitHub Workflow Run State Changed as the trigger and choose where run reports should go.
  • 5Test with one real failed workflow run and confirm the intended Blazemeter master is stopped.

Questions about this workflow

Will it stop a Blazemeter test for every workflow state change?

The prompt should tell Notis to act only when the workflow run has completed with a failure conclusion. The trigger can fire on other status or conclusion changes.

How does Notis know which Blazemeter master to stop?

Specify how to identify the corresponding master in the instruction. The available event descriptions do not provide an automatic GitHub-to-Blazemeter ID link.

Can this stop a test that has already finished?

The action is Stop Master for a specified execution. Have Notis check the relevant execution details before stopping it.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Blazemeter. A trigger fires from one place; an action lands in another.

GitHub 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

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

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

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

TriggerPolling

Create Test

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

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

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

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

TriggerPolling

Get Accounts

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

ActionInstant

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

TriggerPolling

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

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

TriggerPolling

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.

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