Is IDP the same as an agent?

No. IDP structures a document. An agent may call IDP as a tool. Governance still sits on the gateway and the reviewer queue.

Do you skip human review in production?

No. High-confidence fields can auto-post. Money, identity, and policy holds stay on a person until the evals say otherwise.

MuleSoft

The document is the intake. The record is the work.

The first week is in the org, reading what already exists. IDP turns files into fields. Anypoint writes them where the process already lives. A person reviews what the model should not sign. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Send the brief

Five problems

Document work is five jobs, not one model.

01
Classification
What type of document is this
02
Extraction
Which fields · How they relate
03
Validation
Totals · Allowed items · Required parties
04
Human review
Exceptions · Low confidence · Policy holds
05
Integration
Salesforce · ERP · Case or invoice
06
Insights
What failed · What a person had to touch

MuleSoft IDP covers the document lifecycle. Integration and insights belong next to Anypoint and the system of record, not inside the PDF.

Mermaid source

flowchart TD
  A["Classification: what is this file?"] --> B["Extraction: which fields, how related"]
  B --> C["Validation: do the totals hold"]
  C --> D["Human review: exceptions only"]
  D --> E["Integration: write to Salesforce or ERP"]
  E --> F["Insights: what the trail shows"]

Personas

Business user, developer, reviewer.

IDP is not a data-science project. It is an operations desk with a model underneath.

Trust

Einstein for IDP. Trust Layer still applies.

Prompt-based extraction sits behind the same controls as the rest of the Salesforce AI stack. We will not skip that because a demo extracted an invoice.

Adjacent

Composer and RPA sit next to IDP. They are not IDP.

A click-path robot and a document action are different jobs. We will not sell one as the other.

Questions

What we actually say.

Is IDP the same as an agent?: No. IDP structures a document. An agent may call IDP as a tool. Governance still sits on the gateway and the reviewer queue.
Do you skip human review in production?: No. High-confidence fields can auto-post. Money, identity, and policy holds stay on a person until the evals say otherwise.

Doors that belong next.

The brief

Send one document type.

We will tell you whether IDP earns the seat, or whether the file should stay a person.

The document is the intake. The record is the work.

flowchart TD A["Classification: what is this file?"] --> B["Extraction: which fields, how related"] B --> C["Validation: do the totals hold"] C --> D["Human review: exceptions only"] D --> E["Integration: write to Salesforce or ERP"] E --> F["Insights: what the trail shows"]