Power Automate for Manufacturing: Automating Business Central Workflows Without Code

Most manufacturers running Dynamics 365 Business Central already own an automation platform they barely use. Power Automate for manufacturing in Business Central can route raw-material approvals, alert planners to shortages before the first shift, and push production updates into Microsoft Teams, all without writing AL code. Yet in most mid-market plants, the "Automate" menu on Business Central pages goes untouched while planners still chase approvals by email and check stock levels in spreadsheets.

This guide is for operations leaders, BC administrators, and IT managers who already run Dynamics 365 Business Central and want to know four things. It covers which manufacturing workflows can be automated with no code, how to build one step by step, where no-code stops, and what to check on licensing and governance before you scale.

What is Power Automate in Business Central?

Power Automate is Microsoft's low-code workflow service. It connects to Business Central through the Dynamics 365 Business Central connector, which exposes BC data as triggers (events that start a flow) and actions (operations a flow performs). A flow can react to something happening in BC, run on a schedule, or be launched by a user from a BC page. It can then act in BC or in any of the hundreds of other services Power Automate connects to, such as Teams, Outlook, SharePoint and Excel.

Business Central supports five flow patterns that matter for manufacturing:

• Automated (record-based) flows start when a record is created, modified, or deleted in BC, using triggers such as When a record is created (V3). A typical manufacturing use is notifying production planning when a rush sales order lands.
• Business event flows start when a BC business event fires, through the When a business event occurs (V3) trigger. Manufacturers use them to distribute posted invoices or shipment documents automatically.
• Approval flows start when an approval is requested in BC, for example When a purchase document approval is requested (V3). They let managers approve raw-material POs and new items from Teams, Outlook, or mobile.
• Scheduled flows run on a recurrence, such as every weekday at 6:00 a.m. They suit pre-shift shortage reports and daily exception digests.
• Instant flows run when a user selects Automate on a BC list, card, or document page, using the For a selected record (V3) trigger. An example is a one-click "send this item spec to the supplier" action.

Two connector behaviors are worth knowing up front. First, flows are fire-and-forget: the Business Central transaction commits without waiting for the flow to finish. A failed flow never blocks a posting, but it also never rolls one back. Second, every connector step asks for environment and company, so flows can target sandbox and production environments separately. That makes testing safe.

8 manufacturing workflows you can automate in Business Central

Below, common plant-floor and back-office processes are mapped to the connector capability that automates each. They are grouped by the question most guides skip: does the workflow run on standard BC APIs (pure no-code), or does it need a custom API first?

Fully no-code on standard Business Central APIs:

1. Raw-material purchase approval. Triggered when a purchase document approval is requested, the flow routes the PO to the approver in Teams or Outlook and writes the response back to BC.
2. Pre-shift shortage alert. A scheduled flow uses Find records (V3) on items, compares on-hand stock with planner-set minimums, and posts exceptions to a Teams channel.
3. New item / material master approval. Triggered by an item approval request, the flow gets engineering and purchasing sign-off before a new component is used.
4. Supplier onboarding control. Triggered by a vendor approval request, the flow holds new vendors until quality and finance approve.
5. Rush-order notification. Using When a record is created (V3) on sales orders, the flow alerts production planning when an order meets rush criteria.
6. Posted-document distribution. Triggered by a business event such as a posted sales invoice, the flow saves the PDF to SharePoint and emails the customer.
7. Supplier certificate intake. An external trigger, such as an email or a new SharePoint file, files certificates of analysis and updates the related BC record. Whether this stays no-code depends on which BC fields you need to update.
8. Production order released → shop-floor notice. A flow triggered by a production order record or business event creates Planner tasks or a Teams post for the line supervisor. Because production orders aren't part of the standard API set, this one needs a small extension before it can be built without code.

Workflows 1 through 6 can typically go live in days, not weeks, because Microsoft ships templates for most of them. In BC, open the relevant page and select Automate > Power Automate > Create automated flow to see the templates filtered to that page.

Step by step: build a no-code pre-shift shortage alert

This is the highest-value starter flow for most plants. A Teams message lands before the first shift and lists every component below its minimum, so supervisors can re-sequence jobs before they stall mid-run.

Step 1. Create a scheduled cloud flow. In Power Automate, select Create > Scheduled cloud flow. Set the recurrence to run on weekdays about one hour before the first shift.

Step 2. Pull inventory items from Business Central. Add the Business Central action Find records (V3). Choose your environment and company, use the standard API category (v2.0), and select the items table. Filter to inventory-type items so services and non-inventory items are excluded.

Step 3. Get planner-maintained minimums. Keep a simple SharePoint list with two columns: item number and minimum quantity. Add the SharePoint Get items action. Planners can now adjust thresholds without anyone touching the flow, and that ownership is what makes no-code sustainable.

Step 4. Find the exceptions. Use a Filter array step to keep only items whose current inventory is below their minimum.

Step 5. Add a link back to BC. For each exception, the Get url (V3) action can generate a direct link to the Item Card (page 30), so supervisors land on the right record in one click. This action requires Business Central version 22.0 or later.

Step 6. Post the results. Turn the filtered list into an HTML table and post it to the production-planning channel in Teams, or email it to the shift lead.

Step 7. Test in a sandbox, then promote. Point the flow at a sandbox environment first. Before switching to production, change ownership to a service account so the flow doesn't break when an employee leaves.

Total build time for an experienced BC user is typically under two hours, with no developer involved.

Where no-code stops: the production-order boundary

This is the part most Power Automate tutorials leave out, and it matters more in manufacturing than anywhere else.

The Business Central connector works against BC's API pages. The standard API v2.0 set is built around finance, sales, purchasing, items, customers, and vendors. Manufacturing-specific objects such as production orders, routings, production BOMs, and capacity entries generally aren't exposed as standard API entities. That means you can't simply select "production orders" in a connector trigger out of the box. Check your own environment's API list to confirm.

There are three ways around this.

1. Custom API pages. A small AL extension publishes production order data as an API. Microsoft confirms that all connector triggers and actions except approvals work with APIs from extensions, provided they follow API best practices. After that one-time development step, business users can build flows on production data with no code.
2. Custom business events. Developers can add external business events to an extension, such as "production order released" or "output posted." These then appear in the When a business event occurs (V3) trigger. This is usually the cleanest pattern, because events carry business meaning rather than raw table changes.
3. AppSource connectors. Several marketplace apps expose additional BC events to Power Automate. Evaluate them for support, upgrade compatibility, and per-tenant cost.

The practical rule is simple. If a workflow touches sales, purchasing, items, vendors, customers, or finance, start with no-code. If it touches production execution, budget for a small extension first. A Power Platform implementation partner can usually deliver the custom API layer as a short engagement, after which your team owns the flows.

Licensing and governance checklist for manufacturers

Before scaling beyond a pilot, check these six items.

Licensing. Microsoft's BC documentation states that Business Central includes a Power Automate license for using BC data in flows. Industry licensing guides describe this as use rights scoped to the Business Central context. However, Microsoft's setup article for automated flows also lists a Power Automate premium license as a prerequisite. In addition, flows that bring in other premium connectors (SQL, HTTP, third-party MES or WMS systems) need Power Automate Premium. Map each planned flow's connectors against the current Microsoft licensing guide before rollout.

Approvers. Approvers who are licensed BC users can typically respond to approvals from Outlook, Teams, or the Power Automate app without an extra license.

High-volume posting. BC triggers flows through webhooks. When many records change at once, BC sends a collection notification, and the Business Central connector can't process those. In a plant that posts large batches of output or consumption, record-based triggers can silently miss events. Use business events or scheduled flows for high-volume tables.

Business-event webhook refresh. Flows using the When a business event occurs (V3) trigger that were created before June 2024 need their webhook subscription refreshed after a connector security change. Audit older flows.

Security. Flows act with the permissions of the connection owner. Use a dedicated service account with only the permission sets the flow needs, and apply Power Platform data loss prevention (DLP) policies so BC data can't flow to unapproved connectors.

Visibility. Track flow run history alongside operational KPIs. Pairing flows with Power BI dashboards shows leadership whether automation is actually cutting approval cycle times and shortage-driven downtime.

A note for food and agricultural processors

For packers, nut processors, and fresh-produce shippers, "manufacturing" starts at raw intake. Every run has to stay tied to a grower lot for traceability and compliance. The same Power Automate patterns apply, such as intake approvals, quality-hold alerts, and certificate filing. But the underlying data model has to be lot-aware from intake to finished goods. That is where an agriculture-specific ERP makes a difference. Purpose-built production and quality apps record intake, in-process QC, and finished goods against every lot, giving flows clean, traceable events to react to. Teams evaluating this route can start with AgriERP on Business Central.

Ready to put Power Automate to work in your plant?

Most manufacturers can automate their first three workflows on standard Business Central APIs within a few weeks. Production-floor automation becomes possible once a light custom API layer is in place. Folio3 Dynamics has delivered Microsoft Dynamics projects for 20+ years, with 300+ projects worldwide and 200+ Microsoft-certified experts. We implement Power Automate on Business Central from first flow to governed rollout.

Book a Free Power Platform Consultation 

Frequently asked questions

Does Business Central include Power Automate?

Business Central licenses include Power Automate use rights for working with Business Central data. Flows that add other premium connectors, and some automated-flow scenarios, may require Power Automate Premium. Confirm against Microsoft's current licensing guide.

Can I automate production orders in Business Central with Power Automate? 

Yes, but production orders generally aren't available in the standard API set the connector uses. Most implementations add a custom API page or custom business events through a small extension. After that, flows can be built without code.

What's the difference between Business Central workflows and Power Automate? 

BC's built-in workflows handle approvals and simple notifications inside Business Central. Power Automate extends approvals to Teams, Outlook, and mobile, and connects BC to external systems. Any approval workflow you create with Power Automate also appears in BC's workflow list.

Do Power Automate flows slow down Business Central posting? 

No. Flows run asynchronously. The BC transaction commits without waiting for the flow, so a failing flow won't block posting. That also means flows need their own error handling and monitoring.

Which manufacturing workflow should we automate first? 

Start with raw-material purchase approvals or a scheduled shortage alert. Both run entirely on standard APIs, use Microsoft templates or simple steps, and show a measurable impact on cycle time within weeks.