Skip to content
CPQ

Selected UX case · AI Интегратор

AI Integrator

Connecting an external database and importing its data through MagicPad, with explicit decisions wherever the mapping is uncertain.

Preview before import: records checked against system rules, with «Требует правки» and «Дубликат в BP3» statuses

01 Context

Bringing data in from outside BusinessPad.

Integrations live in Settings, split into databases, systems, API and AI services. The AI integrator lets a user start an import by talking to MagicPad instead of configuring it field by field.

Sources include documents, external PostgreSQL databases, applications, reference data and other ERP systems. The designed scenario imports employees from an HR database.

Integrations settings with database connections and MagicPad open on its start screen
Integrations with MagicPad on its start screen.
MagicPad asking where to import data from: document, database, application, reference data or ERP system
The assistant starts by asking where the data comes from.

02 Problem

Mapping someone else’s data model is full of judgement calls.

Source tables rarely match BusinessPad one-to-one. Some columns map with low confidence, some do not exist in the system yet, and some records break its rules: duplicates, invalid emails, values missing from reference lists.

An assistant can propose answers to all of this, but it should not silently write questionable data into typed fields.

03 Design approach

Automate the obvious. Ask about the rest.

The import is a staged wizard with the assistant alongside it. Mapping comes first, split into fields that need a decision, new columns from the source, and matched fields. A preview checks records against the system’s rules, and a final step resolves each problem.

«Далее» stays disabled until every uncertain row has an explicit answer, and the assistant explains why.

New database connection form; MagicPad explains the password is stored in a vault and never seen by the assistant
Credentials go into a form, not the chat, and are stored in a vault.
Connection saved; MagicPad reports the schema it read: employees, counterparties and documents with table and record counts
After connecting, the assistant summarises what it found.

04 Solution

A mapping wizard with an assistant beside it.

Mapping step «Требуют решения»: two existing fields with 68% confidence and no decision yet; «Далее» stays disabled
Mapping, preview and fixing · 1 / 8 · Needs decision
Preview before import: records checked against system rules, with «Требует правки» and «Дубликат в BP3» statuses
  1. 01

    Stepper with sub-steps

    Mapping, preview and fixing, with nested mapping stages.

  2. 02

    Status per record

    Checked, needs edit, or duplicate.

  3. 03

    Assistant explains

    Which records failed which rule, by name.

  4. 04

    Blocked until resolved

    «Далее» is disabled while problems remain.

05 Key decisions

Key decisions

  1. 01

    Secrets stay out of the chat

    Login and password are entered in a secure form; the assistant states it never sees them.

  2. 02

    Uncertainty becomes a decision

    Fields at 68% confidence wait for the user: use the suggestion, change it or leave it empty.

  3. 03

    New columns are opt-in

    Unchecked source columns are not carried over.

  4. 04

    Manual mappings are labelled

    «Сопоставлено вручную» sits next to the AI’s confidence scores.

  5. 05

    Problems are grouped by type

    Duplicates, formats and reference-data gaps each offer their own options.

  6. 06

    The summary is honest

    Selected, created, excluded and error counts, plus what happens to skipped values.

Side panel for a record with an email missing its domain: specify another email, import without email, or skip the employee
Each problem offers a fix, a partial import, or exclusion.
Data fixing step grouped by problem: duplicate, wrong email format, position missing from reference data
All open problems in one place before import is allowed.

06 Outcome

What was designed

An end-to-end Figma flow for AI-assisted database import: choosing a source, connecting securely, reading the schema, mapping fields across three sub-steps, previewing records against system rules, resolving each problem and confirming the result, with side panels for every edit.

Import complete: 3 selected, 1 created, 2 excluded, 0 errors, with follow-up actions in MagicPad
Completion summary with next actions available from MagicPad.