Turn Blazemeter failures into visible GitHub issue labels
Send a Blazemeter failure to Notis and make its related GitHub issue easier to find and triage.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Performance failures can disappear into test reports while the related GitHub issue stays unmarked.
- Bring test failures into the issue's existing triage flow.
- Use labels supplied in the webhook or prompt instead of guessing them.
- Reduce the effort of turning test output into a follow-up.
Setup
Build it in a few focused steps.
- 1Connect Blazemeter and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3In one instruction, tell Notis to use each failure report's supplied repository, issue number, and labels to label the related issue.
- 4Pick the Notis webhook trigger and choose where run reports go.
- 5Test with one real Blazemeter failure webhook and confirm the intended issue and labels.
Questions about this workflow
Does this automation find the related issue automatically?
Only if the webhook or your instruction supplies enough information to identify the repository and issue. Notis should not guess the target issue.
Can Notis create a label that does not exist?
The GitHub action can create labels that do not already exist. Specify the labels you want in the webhook or prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blazemeter to GitHub. A trigger fires from one place; an action lands in another.
Blazemeter triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Blazemeter and GitHub, 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 GitHub.