Skip to content
Notis

Review document extractor options when a Drive file is shared

A newly shared file may need an intake decision. See the available AlgoDocs extractors alongside the sharing event so you can decide what to do next.

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

List document data extractors

Tool to list document data extractors. Use when you need identifiers and names of all extractors in your AlgoDocs account.

Why this helps

Shared documents can sit unnoticed while people try to determine whether they fit an existing extraction workflow.

  • Bring extractor options into the report for a newly shared file.
  • Help reviewers decide whether an existing extractor may apply.
  • Keep the workflow focused on review without changing sharing permissions.

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and AlgoDocs once in the Notis portal.
  • 2Create an automation in the portal or tell Notis the outcome you want in plain language.
  • 3In one instruction, ask Notis to list AlgoDocs extractors and summarize the available options when a file receives new sharing permissions.
  • 4Pick the File Shared trigger and choose where run reports go.
  • 5Test with one real file share and check the report.

Questions about this workflow

Does it inspect or change the new permissions?

The Drive trigger detects newly granted sharing permissions. The AlgoDocs action lists extractors; this workflow does not change permissions or process the file.

Can it determine the right extractor from the file contents?

Only if the trigger data includes useful details. If it does not, the report should state that more context is needed rather than assume what the document contains.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Google Drive triggers

Algodocs actions

Recurring trigger

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

TriggerScheduled

Get Current User

Tool to retrieve current user information. Use after authenticating with your API key to verify identity.

ActionInstant

Webhook trigger

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

TriggerInstant

List document data extractors

Tool to list document data extractors. Use when you need identifiers and names of all extractors in your AlgoDocs account.

ActionInstant

Comment Added (Docs/Sheets/Slides)

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

TriggerPolling

List folders

Tool to list folders. Use when you need to retrieve all folder IDs and their hierarchy. Must be called after obtaining an API key.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

File Deleted or Trashed

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

TriggerPolling

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

File Updated

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

TriggerPolling

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Connect any two apps with Notis in the middle.

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