Skip to content
Notis

Pair Shared Contract Access With Signing Follow-Up

A contract is shared with someone new. Notis checks its Docnify status so access changes do not disappear from your signing follow-up.

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 Document

Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.

Why this helps

Sharing a contract can trigger work across teams, but the signing status is often left in another app and forgotten.

  • Use a sharing event to prompt a relevant status review.
  • Keep signing progress visible after access changes.
  • Receive a report without manually opening both apps.

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and Docnify once in the Notis portal.
  • 2Create an automation and explain how to identify the related Docnify document.
  • 3Pick the Google Drive File Shared trigger.
  • 4Choose where run reports should go.
  • 5Test with one real permission change and verify the document match.

Questions about this workflow

Does this add the new Drive collaborator as a Docnify signer?

No. It fetches the related Docnify document for review. Adding a signer requires a confirmed document and recipient decision.

Can sharing details identify the right Docnify document?

Only when the event and available document information provide a reliable match. Otherwise, the report should call out that it needs confirmation.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Google Drive to Docnify. A trigger fires from one place; an action lands in another.

Google Drive triggers

Docnify actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Document Recipient

Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Document Fields

Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.

ActionInstant

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

Delete Document

Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

Delete Document Field

Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

Delete document recipient

Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.

ActionInstant

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.

TriggerPolling

Get Document

Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

Get Template

Tool to fetch a specific template by its ID. Use to view a template's details and metadata.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

List Documents

Tool to list documents in the Docnify account.

ActionInstant

Connect any two apps with Notis in the middle.

Google Drive and Docnify, 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 Docnify.