Shared Files Auto-Link Contacts to Accounts: Keep Relationships Organized
When you share a file with someone, Notis automatically associates their contact record with the related account in Salesforce. Relationships stay organized without manual work.
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
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
Why this helps
You share a file with a client contact, but they're not linked to their account in Salesforce. Your team later wonders which contacts belong to which accounts.
- Contacts automatically linked to accounts when shared
- Relationships stay accurate without manual updates
- Sales team sees full contact-account picture
- Reduce time spent on CRM hygiene
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Salesforce to Notis.
- 2Tell Notis: 'When I share a file, associate the recipient's contact with the related account in Salesforce.'
- 3Notis will match shared contacts to Salesforce contacts by email.
- 4Share a test file with someone and verify the contact-account link appears.
Questions about this workflow
How does Notis know which account to link?
It matches by company domain or account name. You can refine this by telling Notis how to match them.
What if the contact doesn't exist in Salesforce yet?
Tell Notis to create the contact first, then link it to the account.
Does this work for external folder sharing?
Yes. Notis watches all file sharing, including folder-level permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Salesforce. A trigger fires from one place; an action lands in another.
Google Drive triggers
Salesforce actions
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
File Created
Triggers when a new file is created in Google Drive.
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
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.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
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``.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Not just Google Drive and Salesforce. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Salesforce.