Check Docparser health when a Drive file is shared
A sharing change can mark a document handoff. Notis can check that Docparser is reachable and report the result when new Drive permissions are granted.
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
Ping API
Tool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
Why this helps
A handoff can stall if the next tool connection has quietly stopped working, leaving you to discover the issue later.
- Check Docparser authentication during a Drive sharing event.
- Spot connection issues closer to the handoff moment.
- Get a report without manually opening the Docparser API connection.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Docparser once in the Notis portal.
- 2Create an automation and give it a name.
- 3Tell Notis to check the Docparser API connection when new Drive sharing permissions are granted.
- 4Pick the Google Drive File Shared trigger and choose where run reports go.
- 5Test with one real sharing event and review the report.
Questions about this workflow
Does this check whether the recipient can parse the file?
No. Ping API tests Docparser authentication and connection health. The action does not validate Drive recipient access or parse a file.
Does the sharing trigger include the current permission set?
The listed trigger uses Drive changes with inline permissions and diffs them against previously seen permission keys.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Docparser. A trigger fires from one place; an action lands in another.
Google Drive triggers
Docparser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Parser Models
Tool to retrieve all model layouts for a specific parser. Use when you need to list different layout configurations within a parser that help handle document variations.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
List Parsers
Tool to retrieve all Document Parsers linked to your account. Use when you need to view available parsers or obtain parser IDs for subsequent operations.
File Created
Triggers when a new file is created in Google Drive.
Ping API
Tool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
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 Docparser, 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 Docparser.