Connect Affinda to Dadata ru

When something happens in Affinda, 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 Affinda to Dadata ru

View example

Clean contact details from parsed documents

Send Affinda-extracted contact records to Dadata ru to standardize names, addresses, phone numbers and emails in one pass.

View example

Standardize addresses from parsed invoices

On a schedule, review Affinda-parsed invoice data and use Dadata ru to turn available raw Russian addresses into structured fields.

View example

Validate emails extracted from resumes

When a resume record is sent to a Notis webhook, use Dadata ru to standardize and validate the extracted email address.

View example

Enrich parsed company identifiers

Review available Affinda document records on a schedule and look up supplied Russian company identifiers with Dadata ru.

View example

Structure names extracted from documents

Send an Affinda-parsed full name to a Notis webhook and use Dadata ru to parse its parts, detect gender and return grammatical cases.

View example

Standardize birthdates from parsed records

On a recurring schedule, process available Affinda records and normalize supplied birthdate strings with Dadata ru.

View example

Normalize phone numbers from documents

Use a Notis webhook to pass phone inputs extracted by Affinda to Dadata ru for standardization and validation.

View example

Find companies from parsed email domains

Use corporate email domains found in available Affinda records to retrieve matching company registration details with Dadata ru.

View example

Check passport numbers from parsed documents

Send passport details extracted by Affinda through a Notis webhook to validate the Russian passport number with Dadata ru.

Supported Triggers and Actions

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

Affinda 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.