contract-review-workflow

Contract review workflow

Orchestrates a deployed Mistral Workflow for contract review. Detects wait_for_input() human-in-the-loop checkpoints by querying a status handler, presents findings to the user, and resumes the workflow with their decision via workflow_interact(action: "signal").

Profile note: workflow_execute, workflow_status, and workflow_interact are available in the core profile (default). files_upload (for local PDF upload) requires MISTRAL_MCP_PROFILE=full.

Why workflows vs direct API: the workflow runs durably on Mistral's infrastructure — it persists across restarts, handles retries, and can run multi-step analysis (OCR → clause extraction → legal DB lookup → risk scoring) without keeping a connection open.

Important: handler names are workflow-specific

The name field in workflow_interact calls (signal handler, query handler) is defined by the deployed workflow. Ask the user for:

• The query handler name that exposes checkpoint state (e.g. "get_checkpoint")
• The signal handler name that receives approval decisions (e.g. "human_approval")

Defaults used in the examples below — replace with the actual names from the workflow.

Steps

Step 1 — Collect inputs

Ask the user for:

1. workflowIdentifier — the deployed workflow name or ID (visible in mistral://workflows)
2. The contract document: a file_id (from files_upload, requires full profile) or a public URL
3. Optional: review_type (e.g. "vendor", "employment", "partnership") and language ("fr" or "en")
4. The query handler name and signal handler name (if not the defaults)

Step 2 — Start the workflow

Call workflow_execute:

{
  "workflowIdentifier": "<workflow name or ID>",
  "input": {
    "document_id": "<file_id, or omit if using document_url>",
    "document_url": "<URL, or omit if using file_id>",
    "review_type": "<vendor|employment|partnership|other>",
    "language": "fr"
  }
}

Note the structuredContent.execution_id. Confirm to the user: "Workflow started — execution ID: <execution_id>."