Revenue operations owner
The action waits until this owner approves or denies it.
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.
Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the 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.
Tool call resumes
The customer system imports the approved file and returns its result.
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.
- 01Migration agent requests the import
- 02Deixic checks the source, destination, mapping, and policy
- 03Revenue operations owner decides
- 04Connected customer system returns the import result
Activity history keeps the request, decision, cost, and result.
Keep the procedure for the next request.
Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.