Check caller risk when a Drive file is shared
A newly shared file can contain a number that needs a quick trust check. Let Notis look up the E.164 number with Callerapi and send the result where you review automation reports.
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
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Why this helps
A phone number buried in a shared document can be easy to overlook, leaving you to switch apps and investigate it manually.
- Review caller reputation without opening another tool
- Surface business, carrier, and FTC complaint details when available
- Keep the check tied to the file-sharing event
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Callerapi once in the Notis portal.
- 2Create an automation and name it.
- 3Tell Notis to find the supplied E.164 phone number in the newly shared file, check it with Callerapi, and summarize available caller and spam details.
- 4Choose File Shared (Permissions Added) as the trigger and select where run reports go.
- 5Test with one real shared file that contains an E.164 number.
Questions about this workflow
What kind of phone number should the file contain?
Callerapi's number information action expects a phone number in E.164 format, such as +14155550123.
Will this automation determine which number to check?
Describe the number or context Notis should use in your instruction. If a file has multiple numbers and no clear choice, the automation should report that ambiguity rather than guess.
What information can Callerapi return?
The action can retrieve reputation, business, carrier, and FTC complaint details for a specific phone number.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Callerapi. A trigger fires from one place; an action lands in another.
Google Drive triggers
Callerapi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Information
Tool to retrieve information about the authenticated user, including email and credit usage details. use after authentication to fetch credits spent, monthly allocation, and credits left.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Callerapi, 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 Callerapi.