Connect Google Drive to Blazemeter
When something happens in Google Drive, Notis takes the next step in Blazemeter. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Google Drive to Blazemeter
Send New Test Scripts from Drive to BlazeMeter
When a test script is added to Drive, upload it to the specified BlazeMeter test so it is ready for validation or a run.
Validate BlazeMeter Tests After Drive Asset Updates
When a Drive file tied to a BlazeMeter test changes, ask Notis to validate the identified test and report the result.
Turn Test Review Comments into BlazeMeter Validation Checks
Use a new comment on a Drive document to retrieve validation results for the BlazeMeter test named in the review request.
Adjust a BlazeMeter Monitoring Schedule When a Test Plan Is Shared
When a Drive test plan is shared, update the existing BlazeMeter monitoring schedule identified in your instruction, such as enabling or disabling it.
Register New Drive Test Specifications in BlazeMeter
When a new Drive file is a test specification, create a single BlazeMeter test in the project named in your instruction.
Refresh BlazeMeter Test Details from a Matching Drive Specification
When a new Drive file matches the configured query, update the identified BlazeMeter test using the requested details available in the file.
Remove a Monitoring Schedule When Its Drive Test Plan Is Deleted
When a Drive test plan is deleted or trashed, delete the associated BlazeMeter monitoring schedule identified by your instruction.
Review BlazeMeter Tests Against a Drive Test Catalog
On a recurring schedule, retrieve tests for the project named in your instruction and compare them with the Drive catalog if its contents are accessible.
Stop a Running BlazeMeter Test from an Alert Webhook
Start this workflow from an HTTP request and stop the specified running BlazeMeter test when the request contains a valid master identifier.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Google Drive and Blazemeter
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.