Connect Google Drive to Bolt iot
When something happens in Google Drive, Notis takes the next step in Bolt iot. 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 Bolt iot
Check New Device Guides Before Use
Check a new Drive guide for the Bolt device's online status so setup instructions can be acted on with current connectivity in mind.
Read a Sensor After Procedure Changes
After a Drive procedure changes, check that the target Bolt device is online and read a specified analog pin for a fresh sensor value.
Send a Device Check and Capture Its Reply
Use a new Drive review comment to send a specified ASCII request over Bolt UART and capture the device's immediate response.
Signal a Device When a File Is Shared
When a Drive file or folder gains sharing permissions, set a specified Bolt digital pin high or low to signal a defined handoff.
Reset a Device Signal When a File Is Removed
When a Drive file is moved to trash or permanently deleted, set a specified Bolt digital pin low to clear a signal associated with that file.
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Bolt iot. A trigger fires from one place; an action lands in another.
Google Drive triggers
Bolt iot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Analog Read
Tool to read the analog value from a specified pin on a bolt device. use when you need sensor readings (0–1023) after confirming the device is online.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bolt IoT Digital Write
Tool to set a digital pin high or low on a specified bolt device. use when controlling actuators or leds via digital output.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Check Bolt device online status
Tool to check whether a specified bolt device is online. use when you need to verify device connectivity before sending commands (e.g., control signals). example: 'check if device bolt1234567 is online.'
File Created
Triggers when a new file is created in Google Drive.
Bolt IoT Digital Write
Tool to set a digital pin high or low on a specified bolt device. use when controlling actuators or leds via digital output.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Bolt IoT Serial Read
Tool to read incoming serial data from a bolt device. use when you've initialized uart with serialbegin and need to retrieve serial data.
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.
Bolt IoT Serial Write
Tool to send serial data to a bolt device. use when you need to transmit ascii data over uart after initializing uart with serialbegin.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Bolt IoT Serial Write & Read
Tool to send serial data and read the response on a bolt device. use when you need to transmit ascii data over uart and capture its reply immediately.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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 Bolt iot
Connect any two apps with Notis in the middle.
Google Drive and Bolt iot, 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 Bolt iot.