Update a monitoring schedule when a Drive test plan is shared
A newly shared test plan can trigger a schedule change when your instruction identifies the schedule and the intended update.
Trigger
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Action
Update API Monitoring Schedule
Tool to update the configuration of an existing api monitoring schedule. use when you need to enable or disable a schedule after confirming its id.
Why this helps
A change in access to a test plan can leave a related monitoring schedule in the wrong state unless someone follows up.
- Tie a sharing event to an explicit schedule follow-up.
- Reduce missed schedule changes after collaboration handoffs.
- Keep the requested schedule update visible in run reports.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and BlazeMeter once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, identify the relevant shared test plan, BlazeMeter schedule, and the specific schedule update to make.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real permission change and confirm the intended schedule update.
Questions about this workflow
Will every sharing change update the schedule?
The automation starts on the File Shared event. Describe the relevant file and the exact update to apply; the event does not provide business intent by itself.
Can this create a monitoring schedule?
No. This workflow updates an existing schedule whose identifier and requested change are known.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Blazemeter. A trigger fires from one place; an action lands in another.
Google Drive 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."
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
Create Test
Tool to create a new single test within a specified project. use when registering a new performance test via api.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Get Accounts
Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
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.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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.
Google Drive 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.