A no-code connector pack, built as a per-tenant AL extension, that exposes Business Central triggers and actions to Power Automate, Make, and Zapier so your team can automate cross-app workflows without writing code. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A no-code connector pack, built as a per-tenant AL extension, that exposes Business Central triggers and actions to Power Automate, Make, and Zapier so your team can automate cross-app workflows without writing code.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
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.
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
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.
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.
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.
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.
Buy the license on ecosire.com and download the Power Automate / Make / Zapier Integration Hub for Business Central module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Power Automate / Make / Zapier Integration Hub for Business Central, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Named business-event triggers (e.g. order released, stock below reorder point) | ||||
| Works across Power Automate, Make, AND Zapier | ||||
| Throttling, retry, idempotency and dead-letter delivery handling | ||||
| Field-level payload mapping fitted to your downstream apps | ||||
| Built, installed per-tenant, and supported for you | ||||
| No AL development effort required from your team | ||||
| Adapts to your exact tables, events, and business rules | ||||
| One-time cost (no per-task or per-connector subscription to the integration layer) |
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.
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.
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.
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.
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.
A no-code connector pack, built as a per-tenant AL extension, that exposes Business Central triggers and actions to Power Automate, Make, and Zapier so your team can automate cross-app workflows without writing code.