The export as it ran: dataset, fields, row count, and destination, compared with the approved scope.
Workflows · Customer-data access and export
Put a named data owner in front of a customer export.
Keep a customer-data export behind a named owner: record the requester, dataset, scope, and destination, run the export after approval, and keep the receipt.
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
Export records from customer-data/accounts
The export contains customer information and can move it outside its approved purpose.
- Identity
- data-export · Security
- Target
- customer-data/accounts
- Cost
- Recorded agent cost
- Evidence
- Requested fields and destination
SOC 2 CC6.1
Sensitive: waits for a named approver.
The requested fields and destination, the Data owner's reason, the export result, and the CC6.1 test it supports.
Policy decision
Customer-data exports require the Data owner.
Data owner
The action waits until this owner approves or denies it.
Tool call resumes
The approved export runs against the recorded scope and keeps its result.
Tool call stays blocked
The export stays blocked and the denial remains attached to the request.
Execution order
The agent request stops before the connected tool runs.
- 01Agent requests an export
- 02Deixic checks identity, scope, destination, and policy
- 03Data owner approves or denies
- 04Connected data tool returns the export result
- 05Deixic reads the export back against the approved scope and keeps the receipt
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.