Workflows · Bulk customer imports

Revenue operations reviews the mapping for an 8,421-record import.

Keep the source file, destination, record count, mapping evidence, decision, and import result together.

Request a demo

Agent request

Import 8,421 customer records into the production CRM

A bad mapping can overwrite customer fields or create duplicate production records.

Identity
migration-agent · Revenue operations
Target
production/customer-records
Cost
8,421 records · recorded agent cost
Evidence
Source file, field mapping, duplicate check, and dry-run result

Policy decision

Production customer imports require the Revenue operations owner.

Approver

Revenue operations owner

The action waits until this owner approves or denies it.

Approved

Tool call resumes

The customer system imports the approved file and returns its result.

Denied

Tool call stays blocked

No records are written and the import closes as denied.

Execution order

The agent request stops before the connected tool runs.

  1. 01Migration agent requests the import
  2. 02Deixic checks the source, destination, mapping, and policy
  3. 03Revenue operations owner decides
  4. 04Connected customer system returns the import result

The request, decision, recorded cost, and execution result remain in activity history.

Put this action under policy.

Request a demo.