Connect ActiveMerge to Dadata ru

When something happens in ActiveMerge, 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

Build an automation Browse examples

Examples

Ways Notis can move work from ActiveMerge to Dadata ru

View example

Clean recipient details before document creation

Standardize a recipient's name, address, email, and phone from one submitted record before preparing an ActiveMerge document.

View example

Standardize an address for document delivery

Clean a raw Russian postal address submitted by webhook so document delivery details have a consistent structure.

View example

Check a signer email before document preparation

Validate and classify a user-provided email before it enters an ActiveMerge document preparation workflow.

View example

Parse a recipient name for formal documents

Standardize a submitted full name, detect gender, and return grammatical cases for formal document text.

View example

Enrich a company record from its registration ID

Look up registered company or entrepreneur details from a supplied INN, OGRN, or KPP for business document preparation.

View example

Identify a company from a corporate email

Use a corporate email domain to retrieve company registration details before preparing business documents.

View example

Normalize a birthdate for a document record

Standardize and validate a captured birthdate into yyyy-mm-dd before it is used in a document record.

View example

Validate passport details before document preparation

Check a submitted Russian passport number against the official registry before relying on it in a document workflow.

View example

Standardize a contact phone for document follow-up

Convert a collected phone number into a validated 11-digit format for consistent contact records around a document workflow.

Supported Triggers and Actions

Notis builds workflows that link ActiveMerge to Dadata ru. A trigger fires from one place; an action lands in another.

ActiveMerge triggers

Dadata ru actions

Recurring trigger

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

TriggerScheduled

Clean Address

Standardizes a Russian postal address and parses its components.

ActionInstant

Webhook trigger

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

TriggerInstant

Clean Birthdate

Standardizes birthdates and reports whether they could be parsed.

ActionInstant

Clean Email

Cleans and validates an email address, correcting common domain typos.

ActionInstant

Clean Name (FIO)

Parses and standardizes a full name, with gender and grammatical forms.

ActionInstant

Clean Passport

Checks a Russian passport number against the official registry.

ActionInstant

Clean Phone

Standardizes and validates a phone number.

ActionInstant

Clean Vehicle

Identifies and standardizes a vehicle's make and model from text.

ActionInstant

Clean Composite Record

Standardizes contact records containing multiple types of data.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.