Check new Drive sharing recipients against your CRM
See whether a newly added Drive collaborator is already known to your team.
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
Search People
Tool to retrieve people matching search criteria. use when you need to find specific contacts by name, email, or phone after authenticating with your api key.
Why this helps
New collaborators can be external leads or customers, but their identity may be unfamiliar when access is granted.
- Search CRM people using recipient email details in the permission change.
- Surface known contacts alongside the shared file context.
- Avoid treating a permission grant alone as proof of a sales relationship.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and CentralstationCRM once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for recipient checks.
- 3In one instruction, ask Notis to search CentralstationCRM for each newly added sharing recipient with an available email address and report matches.
- 4Pick File Shared (Permissions Added) and choose where run reports go.
- 5Test with one real permission change and inspect the report.
Questions about this workflow
What recipient information is available?
The trigger uses Drive changes with the current permission set, then compares it with previously seen permissions. Ask Notis to use only recipient details present in the event.
Will it add recipients to the CRM?
This workflow searches for existing people and reports matches. A share by itself does not establish that someone should become a CRM contact.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Centralstationcrm. A trigger fires from one place; an action lands in another.
Google Drive triggers
Centralstationcrm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Connection
Tool to verify the connection status of the centralstationcrm api key. use when validating credentials before making other api calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Count People
Tool to retrieve the total number of people in the account. use when you need the current total number of contacts in your centralstationcrm account. example: "how many contacts exist in my account?"
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Company
Tool to create a new company record. use when you need to add an organization to your crm before linking it to contacts or deals.
File Created
Triggers when a new file is created in Google Drive.
Create Deal
Tool to create a new deal record. use when needing to log a sales opportunity after grouping contacts or companies.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create Person
Tool to create a new person record. use when you need to add a person to your crm before linking them to other records.
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 Person Address
Tool to create a new address for a specific person. use when you need to add or update postal details after confirming person id.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Create Person Assistant
Tool to create a new assistant (assi) entry for a specific person. use after confirming the person id when you need to manage assistant contacts.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create Person Avatar
Tool to create a new avatar for a specific person. use when you need to attach a base64-encoded image file after confirming the person's id.
Connect any two apps with Notis in the middle.
Google Drive and Centralstationcrm, 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 Centralstationcrm.