Power Automate / Make / Zapier Integration Hub for Business Central

Key Features

Pre-built BC triggers (order released, shipment/invoice posted, contact created, stock below reorder point) implemented as AL event subscribers

Named connector actions (create/update customer, item, sales order, journal line) callable from Power Automate, Make, and Zapier

Outbound webhook event publisher with signed payloads and a retry-backed delivery log table

Power Automate custom connector definition (OpenAPI 2.0) configured for your tenant with S2S/OAuth auth

Private Make and Zapier app definitions wired to your BC environment

Field-level mapping templates so each payload carries exactly the fields downstream systems require

Throttling and retry handling via the BC job queue to respect Microsoft API rate limits and guarantee delivery

Idempotency keys and dead-letter handling so retried events never double-post downstream

Per-tenant AL extension install with dedicated permission sets (no AppSource dependency)

Admin page in BC to enable/disable events, view delivery status, and re-send failed webhooks

Dataverse / Power Platform bridge option for flows that need virtual tables

Sandbox-first validation and end-to-end testing before production cutover

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Microsoft Dynamics 365 Business Central ships with a capable REST/OData v4 API and a standard Power Automate connector, but the out-of-the-box surface rarely matches how your business actually fires events. You can read and write entities, yet there is no clean way to say "when a sales order is released, post to Slack, create a Make scenario, and update a Zapier-connected CRM" without custom AL development and careful event plumbing.

This Integration Hub closes that gap. ECOSIRE builds a per-tenant AL extension (table extensions, page extensions, and event subscribers on the documents you care about) that publishes meaningful business events — order released, shipment posted, invoice registered, customer created, item stock below threshold — as outbound webhooks and as discrete, named connector actions. Power Automate consumes them through a custom connector; Make and Zapier consume them through published private app definitions we configure for your account.

Because this is build-to-order, nothing is generic. We scope which tables and events matter, design field-level mapping templates so each payload carries exactly the fields downstream apps expect, and wire throttling and retry handling against the BC job queue so bursts never trip Microsoft's API limits or lose events. We install it as a per-tenant extension (not an AppSource listing), assign permission sets, configure the OAuth/S2S authentication for each platform, and validate end-to-end in your sandbox before production.

You receive working automations, the connector definitions, documentation, and a supported extension on your own environment. No instant download — a real, fitted integration delivered and maintained by engineers who know AL.

What you get

Per-tenant Business Central AL extension (.app) installed on your sandbox and production environments

Configured Power Automate custom connector (OpenAPI definition) registered to your tenant

Private Make and Zapier app definitions connected to your BC environment

Field-level payload mapping templates for each agreed event and action

BC permission sets and Microsoft Entra / S2S authentication setup for each platform

Webhook delivery + retry log page and admin configuration page inside Business Central

Technical documentation, event/action reference, and an admin runbook

End-to-end tested sample flows/scenarios/zaps demonstrating each automation

Who this is for

Operations Manager

Wants to stop copying data between Business Central and the team's other apps. Needs reliable, no-code automations — order-to-Slack, invoice-to-CRM — that non-developers can extend in Power Automate or Zapier afterward.

IT / Power Platform Admin

Owns the tenant and worries about API limits, authentication, and governance. Needs a clean per-tenant extension with proper permission sets, S2S auth, and a delivery log they can audit rather than ad-hoc unmanaged flows.

Business Central Partner / Consultant

Delivering a BC project and needs a fitted integration layer fast. Wants ECOSIRE to build and support the AL connector pack so they can focus on the customer's core ERP configuration.

How Power Automate / Make / Zapier Integration Hub for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Named business-event triggers (e.g. order released, stock below reorder point)	Included	Partial support	Partial support
Works across Power Automate, Make, AND Zapier	Included	Partial support	Partial support
Throttling, retry, idempotency and dead-letter delivery handling	Included	Partial support	Partial support
Field-level payload mapping fitted to your downstream apps	Included	Included	Not included
Built, installed per-tenant, and supported for you	Included	Not included	Partial support
No AL development effort required from your team	Included	Not included	Included
Adapts to your exact tables, events, and business rules	Included	Included	Not included
One-time cost (no per-task or per-connector subscription to the integration layer)	Included	Partial support	Not included

Frequently Asked Questions about Power Automate / Make / Zapier Integration Hub for Business Central

How long does delivery take and how is it installed?

Typical build-to-order delivery is 2 to 4 weeks depending on how many events, actions, and downstream platforms you need. We start by scoping the tables and triggers, build the AL extension, then install it as a per-tenant extension on your sandbox for end-to-end validation before promoting to production. You are not downloading an AppSource app — ECOSIRE builds, installs, and verifies it on your specific environment.

Do you support the extension and provide updates after delivery?

Yes. The per-tenant extension is supported by ECOSIRE. We monitor compatibility with Business Central's twice-yearly major releases (and monthly updates), update the AL code and connector definitions when Microsoft changes the API or event surface, and handle changes you request — new events, new mappings, additional platforms. Support and update terms are agreed at purchase; we can also hand over documentation for your own admins.

Does this work on Business Central SaaS (cloud) or only on-premises?

It is built for Business Central online (SaaS) as a per-tenant extension and uses the standard REST/OData API plus Microsoft Entra S2S/OAuth authentication. On-premises and hybrid deployments can be supported too, with the authentication and webhook egress adjusted to your network — we confirm the exact approach during scoping.

Will the webhooks and connector calls hit Microsoft's API rate limits?

We design around them. Outbound delivery runs through the BC job queue with throttling, exponential-backoff retries, idempotency keys, and a dead-letter log, so event bursts are smoothed out and nothing is silently lost. Inbound actions from Power Automate, Make, and Zapier are batched and paced to stay within Business Central's documented limits.

Why not just use the standard Power Automate connector for Business Central?

The standard connector exposes generic CRUD over entities, but it does not fire on the specific business events most teams care about (such as 'order released' or 'stock below reorder point'), and it leaves payload shaping, retry handling, and Make/Zapier coverage to you. This Hub adds named event triggers via AL event subscribers, curated field mappings, guaranteed delivery, and ready-to-use Make and Zapier app definitions — fitted to your workflows.