Create Callingly webhooks from shared Drive specifications
When a teammate shares a complete webhook specification, let Notis create the webhook in Callingly from its details.
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
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".
Why this helps
A complete integration specification can be shared with the team but still require someone to remember the setup task.
- Start webhook setup from a shared specification.
- Reduce manual transfer of the URL and event details.
- Skip a shared file that lacks the necessary configuration.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Callingly once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Describe that a newly shared webhook specification with a target URL and event configuration should create a Callingly webhook; skip incomplete specifications.
- 4Pick the Google Drive File Shared trigger and choose where run reports go.
- 5Test with one real shared specification containing the URL and event details.
Questions about this workflow
What details must be present?
The shared specification should identify the target URL and the Callingly events the webhook should cover.
Will sharing any file create a webhook?
No. Use a prompt that only applies to a webhook specification with the required configuration.
When this happens · Trigger
Do this · Action
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.
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.