Connect Google Docs to Dadata ru
When something happens in Google Docs, Notis takes the next step in Dadata ru. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Google Docs to Dadata ru
Standardize addresses when a Google Doc form is filled
Clean and structure Russian postal addresses as soon as a document placeholder is completed.
Clean lead emails found in Google Docs
Validate and normalize email addresses in documents that match your search.
Parse client names whenever a Google Doc changes
Extract structured names, gender, and grammatical forms from updated document text.
Normalize phone numbers when a document reaches a threshold
Validate and standardize phone numbers once a Google Doc passes your word or character limit.
Look up a company when its tax ID appears
Find Russian company or entrepreneur details when a keyword event identifies a new identifier.
Suggest addresses for each new Google Doc
Use Dadata address suggestions to help review partial addresses in newly created documents.
Extract vehicle details after a document structure change
Parse vehicle information when tables or images change in a monitored Google Doc.
Validate passport details before a source document is deleted
Run a passport validation action when a monitored Google Doc is moved to trash.
Classify business activity when a root folder is created
Use OKVED2 suggestions to help classify new business folders and their initial documents.
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Dadata ru. A trigger fires from one place; an action lands in another.
Google Docs triggers
Dadata ru actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clean Address
Tool to clean and standardize russian postal addresses. use when you need structured address fields from raw strings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Clean Birthdate
Tool to standardize and validate birthdate strings. use after capturing raw birthdate inputs to normalize them to yyyy-mm-dd.
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.
Clean Email
Tool to standardize and validate email addresses. use when you have raw email input and need to fix typos, correct domains, and classify as personal, corporate, or disposable. use after collecting user-provided emails.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
Clean Name (FIO)
Tool to standardize and parse full names (fio), detect gender, and return grammatical cases. use when you need structured name parsing and declensions from raw fio inputs.
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.
Clean Passport
Tool to validate a russian passport number against the official registry. use after collecting passport details.
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.
Clean Phone
Tool to standardize and validate phone numbers. use when you need to convert arbitrary phone inputs into a uniform, validated 11-digit format for further processing.
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
Clean Vehicle
Tool to standardize and parse vehicle data fields. use after obtaining raw vehicle info to extract brand, model, year, vin, and other identifiers.
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
Find Address
Tool to find address by identifier. use when you need full address details from a cadastral number, fias id, or kladr code.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Google Docs and Dadata ru
Connect any two apps with Notis in the middle.
Google Docs and Dadata ru, 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 Dadata ru.