Types of Business Process Automation

App integration and rule-based workflows

An app integration moves structured information through supported connections. For example, an approved project record can create a task in the team’s project tool. A rule checks whether required fields exist and chooses the correct destination. This works well when systems expose reliable connections and use stable record IDs.

Approval workflows add a controlled waiting step. The system prepares the request, assigns a reviewer and records the decision. It needs a rule for rejection and non-response as well as approval. A reminder can prompt a reviewer, but it should not silently turn a missing decision into consent.

Desktop and browser automation

Desktop automation interacts with an application’s interface, such as entering information into a legacy system. It may be useful where a supported integration is unavailable. It also depends on the interface, session and permissions remaining suitable for the task.

Assess how the process behaves when a dialog appears, a layout changes or a session expires. A robust design stops for unexpected states and gives the operator enough information to recover. Use authorised access and the application’s permitted methods; automation does not remove account or usage restrictions.

Document and AI-assisted automation

Document generation fills approved templates from known fields. Extraction reads information from existing documents, often requiring checks for missing or uncertain values. Routing moves a file to the correct person or location. A business may need all three, but they should be tested separately.

AI assistance is useful for varied language, such as preparing a summary of a long request. Its output can vary and may be wrong. Define the evidence the reviewer will see and the actions the model is allowed to suggest. A model-generated category should not automatically authorise a consequential business decision.

Combine methods in a worked example

Consider a supplier onboarding process. A form collects structured details. A document step prepares a review sheet. An approval workflow asks the purchasing owner to accept or reject the supplier. A supported integration creates the approved record in the purchasing system. If that system only supports a permitted desktop workflow, a controlled desktop step may be considered instead.

An AI summary of the supplier’s description could assist the reviewer, but it is optional. The core process can still work without it. The best combination is the smallest one that reliably achieves the required outcome.

Compare maintenance as well as capability

For each option, ask who maintains it, how failures are noticed and whether the team can trace a case. Test a changed field, a repeated request and a failed connection. Include the effort needed to keep templates, permissions and business rules current.

Automations For Business can help choose and connect the appropriate methods around your tools, with human review built into the process. Bring the input, output and awkward cases. A custom design should follow those needs rather than force every task into the same type of automation.

Your ready-to-use checklist

Make the next step clear.

Sources and notes

Sources checked on October 22, 2026.

• Microsoft: approval flows

  Official documentation for combining an automated flow with a person’s approval.

• Microsoft: test cloud flows

  Official guidance for testing automation before relying on its output.

• NIST: Generative AI Risk Management Profile

  A primary reference for assessing generative AI risks and evaluating its use.