Power Automate

Get the file contentCopy Anchor Link

After the trigger, add SharePoint → Get file content with File Identifier set to the trigger's Identifier. The action is referenced as Get_file_content in expressions.

Add the HTTP actionCopy Anchor Link

And as Body:

{
  "file_base64": "@{base64(body('Get_file_content'))}",
  "filename": "@{triggerOutputs()?['body/{FilenameWithExtension}']}",
  "options": {
    "expect": "invoice",
    "export": ["xlsx"],
    "language": "en",
    "metadata": { "source": "power-automate" }
  }
}

The Idempotency-Key header uses the run identifier: if the HTTP action retries under its retry policy, Constaia returns the stored response without charging twice. More in Idempotency. The options are in POST /v1/analyze.

Check the status codeCopy Anchor Link

If the analysis does not finish within 30 s (long PDFs), the API responds 202 with status: "queued" or "processing" and no verdict. Add a Condition with @{outputs('HTTP')?['statusCode']} equal to 200 before continuing, or use "async": true and receive the result by webhook (below).

Errors (4xx, 5xx) make the HTTP action fail. To handle them, add a branch with Configure run after → has failed and read body('HTTP')?['error']?['code'] and body('HTTP')?['error']?['request_id']. The codes are in Errors.

Parse the response with Parse JSONCopy Anchor Link

Add Parse JSON with Content @{body('HTTP')} and this schema (only the part you use; undeclared properties are still available in body('HTTP')):

{
  "type": "object",
  "properties": {
    "id": { "type": "string" },
    "status": { "type": "string" },
    "document": {
      "type": ["object", "null"],
      "properties": {
        "type": { "type": "string" },
        "label": { "type": "string" },
        "confidence": { "type": "number" }
      }
    },
    "verdict": {
      "type": ["object", "null"],
      "properties": {
        "status": { "type": "string" },
        "reasons": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "code": { "type": "string" },
              "severity": { "type": "string" },
              "message": { "type": "string" }
            }
          }
        }
      }
    },
    "fields": { "type": "object" },
    "warnings": { "type": "array", "items": { "type": "string" } },
    "exports": { "type": "object" }
  }
}

Route with a SwitchCopy Anchor Link

Add a Switch on @{body('Parse_JSON')?['verdict']?['status']} with three cases:

Each extracted field is an object with value, confidence, validated and source. More in Verdicts and Exports.

Create the receiving flowCopy Anchor Link

Create a flow with the When a HTTP request is received trigger. Under Who can trigger the flow? choose Anyone (Constaia doesn't authenticate with Microsoft Entra) and use as Request Body JSON Schema:

{
  "type": "object",
  "properties": {
    "type": { "type": "string" },
    "created_at": { "type": "string" },
    "data": { "type": "object", "properties": { "id": { "type": "string" } } }
  }
}

Save the flow, copy the generated URL and register it in the dashboard or with POST /v1/webhook-endpoints (see Webhooks). If the flow has no Response action, the trigger answers 202 Accepted right away, which Constaia counts as a successful delivery.

Read the analysis againCopy Anchor Link

Power Automate has no function to compute the HMAC-SHA256 signature, so don't trust the event body:

1. Condition: @{startsWith(triggerBody()?['data']?['id'], 'an_')} is true.
2. HTTP GET to https://api.constaia.com/v1/analyses/@{triggerBody()?['data']?['id']} with the Authorization header.
3. Parse JSON with the schema above and the same Switch.

The API only returns analyses of your account: a forged event can at most make you re-read one of your own analyses. For batch.completed, data.id starts with bat_ and the read is GET /v1/batches/{id}.

Drop duplicatesCopy Anchor Link

Constaia retries failed deliveries for about 3 days with the same webhook-id, available in @{triggerOutputs()?['headers']?['webhook-id']}. Store it (for example in a SharePoint list or a Dataverse table) and end the flow if it already exists.