Verify the AlgoDocs account before document operations
Give every inbound document workflow a known account context before processing begins.
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
Automations can run against the wrong connected account when identity is not checked first.
- Confirms the active AlgoDocs account
- Adds a reliable first step to inbound workflows
- Makes run reports easier to audit
Setup
Build it in a few focused steps.
- 1Connect Google Docs and AlgoDocs in Notis once.
- 2Create an automation that verifies the AlgoDocs user for each inbound request.
- 3Tell Notis to call the current user action and report the identity before continuing.
- 4Pick a Notis webhook trigger and choose a report channel.
- 5Send one real webhook request to test the check.
Questions about this workflow
What starts this workflow?
An HTTP request sent to the Notis webhook starts it.
Why verify identity first?
It confirms which AlgoDocs account is connected before document-related decisions are made.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Algodocs. A trigger fires from one place; an action lands in another.
Google Docs 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.
New Document Created
Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.
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.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
Document Placeholder Filled
Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.
Document Search Update
Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.
Document Structure Changed
Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
Connect any two apps with Notis in the middle.
Google Docs 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.