Back to workflows
FinanceOrchestrate multiple stepsTeam

Procurement intake orchestration

Classify a purchase request, collect missing evidence, and route the right approval path.

What this workflow does

Classify a purchase request, collect missing evidence, and route the right approval path. It coordinates dependencies across connected systems, pauses at exception boundaries, and records the state of every approved sub-step.

What you gain

Complete procurement case with assigned approvals

What the AI agent changes

How this worked before

A fixed workflow required every system and input to behave exactly as expected; one exception stopped the entire chain.

What the AI agent changes

The agent chooses the next tool from the current state, recovers from common exceptions, and asks for a decision at the right boundary.

Agent trigger

A new purchase or vendor request is submitted.

Inputs

  • Process context: request, vendor, budget, security, and legal data
  • Approved policies, ownership, and exception rules

Agent flow

  1. 1

    Build the dependency graph and verify every connector permission.

  2. 2

    Coordinate read-only sub-steps and surface blocked dependencies.

  3. 3

    Prepare the complete approval route and exception list with state, exceptions, and rollback points.

  4. 4

    Execute approved sub-steps idempotently and verify the final state.

Human decisions

After step 3

The accountable process owner approves the complete approval route and exception list.

Outcome

  • Complete procurement case with assigned approvals
  • Evidence, exceptions, and audit trail

Guardrails

  • Pause when a dependency or approval is missing.
  • Record before-and-after state for every system write.

Risks and mitigations

A partial multi-system execution can leave records in conflicting states.

Use idempotency keys, checkpoints, and explicit compensation for every write step.

Sources and evidence