# Flow use cases

> Six processes built on the Flow canvas, from order intake to screening checks, with the nodes each one uses.

These processes are built on the Flow canvas. In each one, something comes in, an AI agent decides what to do, and APIs carry out the decision. They are examples, not step-by-step instructions.

## Order intake and enrichment

What happens: an order or a sales lead arrives. An agent validates it, checks stock and the customer's credit over API, and creates the order in the enterprise resource planning (ERP) or customer relationship management (CRM) app.

You use: a [connector trigger](node-connector-trigger.md), [HTTP Request](node-http-request.md), an [Autonomous agent](node-agent.md), a [Decision](node-decision.md), and [connectors](popular-connectors.md).

![The order intake process on the Flow canvas after a debug run: New order, Check stock, Check credit, Review order, and Accepted?, which branches to Create order in CRM and Notify sales rep. The bottom toolbar shows Maestro Orchestrate, and the debug panel lists the run's execution trace and variables.](https://dev-assets.cms.uipath.com/assets/images/maestro/order-intake-debug-run-orchestrate-42767856.webp)

## Claim triage

What happens: a first notice of loss arrives, which is the first report of an insurance claim. An agent classifies its severity, checks the coverage against the policy system's API, and routes the claim to the right adjuster's queue.

You use: a [connector trigger](node-connector-trigger.md), an [Autonomous agent](node-agent.md), [HTTP Request](node-http-request.md), a [Switch](node-switch.md) to route by severity, and [Queue tools](node-queue-tools.md).

## Service desk request fulfillment

What happens: an employee asks for help, for example a password reset or access to an app. An agent reads the request, pulls the employee's context from the identity, IT service management, and human resources (HR) systems over API, decides what to do, and carries it out.

You use: an [Autonomous agent](node-agent.md) or a [Conversational agent](node-conversational-agent.md) (Preview), [HTTP Request](node-http-request.md), and [connectors](popular-connectors.md). [Build a chat agent workflow](build-a-chat-agent-workflow.md) shows the chat version step by step.

## Invoice intake

What happens: an invoice arrives as a document. An extraction step reads its fields, an agent checks them against the purchase order over API, and the invoice is posted when it matches.

You use: [Extract](node-extract.md) (Preview), an [Autonomous agent](node-agent.md), [HTTP Request](node-http-request.md), and a [Decision](node-decision.md).

## Transaction reconciliation

What happens: APIs pull both sides of a transaction, for example the bank record and the ledger entry. When they don't match, an agent explains the difference and proposes a fix, and the process either applies the fix over API or hands it to a person.

You use: [HTTP Request](node-http-request.md), an [Autonomous agent](node-agent.md), a [Decision](node-decision.md), and [connectors](popular-connectors.md).

## Screening check

What happens: a new customer signs up. An agent runs sanctions and adverse-media lookups over API, scores the result, and writes the score back to the customer record. Customers with a match are flagged for review.

You use: a [connector trigger](node-connector-trigger.md), [HTTP Request](node-http-request.md), an [Autonomous agent](node-agent.md), and a [Decision](node-decision.md).

## Related pages

- [Your first Flow](quickstart.md): build a working process on the Flow canvas.
- [Node reference](flow-node-reference.md): every node these use cases mention.
- [Choosing a canvas](choosing-a-maestro-modeler.md): build the same processes on the Case or BPMN canvas.