Check which AlgoDocs account Notis is connected to
When account access is unclear, send a request and get the current user information from the authenticated AlgoDocs connection in your run report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Current User
Tool to retrieve current user information. Use after authenticating with your API key to verify identity.
Why this helps
Uncertainty about which account a connection uses can slow down setup and make it harder to trust later document workflows.
- Retrieve the current user details from the connected AlgoDocs account.
- Use a simple webhook request to run the check when needed.
- See the result in your chosen report channel.
Setup
Build it in a few focused steps.
- 1Connect AlgoDocs once in the Notis portal with your API key.
- 2Create an automation in the portal or tell Notis the outcome you want in plain language.
- 3In one instruction, ask Notis to retrieve the current AlgoDocs user information and report the account identity.
- 4Pick a webhook trigger and choose where run reports go.
- 5Send one test request and confirm the returned identity is expected.
Questions about this workflow
Does this validate my API key?
The action retrieves current user information after authentication. A successful response confirms the connection can retrieve that information; it is not a broader permissions audit.
How does the workflow start?
A Notis webhook starts it when it receives an HTTP request.
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.
Get Current User
Tool to retrieve current user information. Use after authenticating with your API key to verify identity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List document data extractors
Tool to list document data extractors. Use when you need identifiers and names of all extractors in your AlgoDocs account.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
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 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.