Schedule Bolna calling batches from Drive campaign files
Use a campaign file as the handoff that tells Notis which prepared Bolna batch is ready to schedule.
Trigger
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Action
Schedule batch by id
Schedule a batch for calling via agent
Why this helps
Prepared calling batches can be easy to overlook when their campaign files live in a separate workspace.
- Use a new campaign file as a scheduling signal.
- Keep campaign context alongside the batch handoff.
- Avoid manually revisiting Bolna to schedule a ready batch.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Bolna once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis: When a new file matching my campaign query appears, schedule the existing Bolna batch with the ID stated in the file or this instruction.
- 4Pick the Google Drive New File Matching Query trigger and provide the query through the trigger setup.
- 5Choose where run reports should go, then test with one real campaign file and batch ID.
Questions about this workflow
Does this workflow create a batch?
No. The action schedules a batch by ID, so the batch must already exist in Bolna.
Where does the batch ID come from?
Include the ID in the Drive file or in your instruction to Notis, and test that the intended batch is scheduled.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Bolna. A trigger fires from one place; an action lands in another.
Google Drive triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Fetch all batches by agent id
List all batches for agent
File Created
Triggers when a new file is created in Google Drive.
Get all agents
List all agents
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Get all phone numbers
List all phone numbers for your account
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 execution by id
Retrieve specific execution by `execution id`
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Make a phone call from agent
Initiate calls
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
Google Drive and Bolna, 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 Bolna.