Connect Google Drive to Callingly
When something happens in Google Drive, Notis takes the next step in Callingly. 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 Callingly
Turn a new Drive lead brief into a Callingly call
Create a Callingly outbound call when a new Drive file contains the lead details and call instructions.
Create a Callingly agent from a Drive intake file
Register an agent in Callingly when a new Drive intake file supplies the account and contact details.
Create a Callingly client from a Drive intake
Create a Callingly client when a new Drive onboarding file contains the client information needed for setup.
Create a Callingly team from a Drive setup request
Start team creation when a new Drive setup request explicitly includes the required team configuration.
Create a Callingly webhook from a Drive request
Create a Callingly webhook from a new Drive request that specifies the target URL and event details.
Apply a documented Callingly client activation decision
Use a new Drive comment to activate or deactivate a client only when it names the client id and clearly states the decision.
Call a lead when a Drive brief is shared
Start a Callingly outbound call when a newly shared lead brief contains contact details and a clear call request.
Start a Callingly call when lead instructions change
Create a Callingly outbound call after a Drive file update adds clear call instructions and the required lead details.
Call leads from Drive files matching a saved query
Create a Callingly outbound call when a newly matching Drive file contains the lead details and a clear call request.
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Callingly. A trigger fires from one place; an action lands in another.
Google Drive triggers
Callingly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Activate/Deactivate Client Account
Tool to activate or deactivate a client account. use when you need to toggle client access after onboarding or offboarding. example: "activate client 123" or "deactivate client 456".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Agent
Tool to create a new agent. use when you need to register an agent in callingly after gathering their account id and contact details.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead details.
File Created
Triggers when a new file is created in Google Drive.
Create Client
Tool to create a new client. use when adding a new client to your callingly account.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create Team
Tool to create a new team. use when setting up a team configuration before adding agents.
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.
Create Webhook
Tool to create a new webhook for call or lead events. use when you need to receive real-time notifications on specific events. example: "create a webhook for call completed events to http://example.com/callback".
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Delete Agent
Tool to delete an agent. use when permanently removing an agent after confirming the agent id.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Delete Client
Tool to delete a client. use when you need to remove an existing client from your account after confirming its id.
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 Callingly
Connect any two apps with Notis in the middle.
Google Drive and Callingly, 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 Callingly.