Update Blazemeter tests from Coda page updates
Let the planning page drive approved changes to the live test configuration.
Trigger
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
Action
Update Test
Tool to update details of a specific test by its id. use when you need to modify test configuration or name of an existing test after confirming its id. example: "update the test name to 'loadtest' for test with id '12345'."
Why this helps
Test settings drift when documentation changes are not carried into the performance platform.
- Reduces configuration drift
- Keeps change intent documented
- Avoids duplicate editing
Setup
Build it in a few focused steps.
- 1Connect Coda and Blazemeter once in Notis.
- 2Create an automation describing which approved page changes should update the test.
- 3Pick Specific Coda Page Updated as the trigger.
- 4Choose a report channel and test with one real update.
Questions about this workflow
Will every page edit change the test?
Only changes covered by your instruction should result in an update, and Notis can request confirmation when details are unclear.
Can it rename a test?
Yes, the Update Test action supports changing test details such as the name after the id is confirmed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Coda to Blazemeter. A trigger fires from one place; an action lands in another.
Coda 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."
Coda Document Deleted Trigger
Triggers when a Coda document is deleted.
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.
New Coda Document Trigger
Triggers when a new Coda document is created.
Create Test
Tool to create a new single test within a specified project. use when registering a new performance test via api.
New Coda Page Trigger
Triggers when a new page is added to a Coda document.
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.
Specific Coda Page Updated Trigger
Triggers when a specific page within a Coda document is updated.
Get Accounts
Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
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.
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.
Coda 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.