产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $499.00 USD
- dynamics_365_business_central 版本
- —
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Power Automate / Zapier Integration Hub
A per-tenant Business Central extension that exposes rich event triggers and create/update/find actions to Power Automate, Zapier and Make, with a built-in webhook publisher and field-mapping engine. Built, installed and supported by ECOSIRE on your BC environment.
$499.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Pre-built event triggers for BC business events (sales/purchase order released, customer/vendor created, item ledger posted, approval requested, payment registered) surfaced as clean Power Automate, Zapier and Make triggers
Record actions to create, update, find/upsert and delete BC entities (customers, items, sales orders, journal lines) callable from any of the three platforms
Ready-to-import connector templates and example flows for Power Automate, Zapier and Make so your team starts from a working blueprint, not a blank canvas
Outbound webhook publisher that fires signed JSON payloads to any HTTPS endpoint, with HMAC signature, retry-with-backoff and a dispatch log for replay
Field mapping and transform engine — map BC fields to target schemas with type casts, lookups, constants, conditional skips and value translation tables, configurable without redeploying code
Built on AL event subscribers, table/page extensions and bound API pages over the BC REST/OData v4 API for stable, upgrade-safe integration points
Optional Dataverse virtual-table surfacing for tighter native Power Platform / Power Apps integration when you run on the Microsoft stack
Job Queue-based dispatch with throttling and retry so high-volume events never overload the Business Central service tier
Dedicated permission sets plus Microsoft Entra (Azure AD) OAuth app registration for least-privilege, auditable access
Inbound idempotency keys and duplicate-suppression so retried flows don't create double records in BC
Per-connector enable/disable toggles and a setup page to manage endpoints, secrets, mapping profiles and active triggers
Structured error capture with a retry/dead-letter view so failed automations are visible and recoverable, not silently dropped
Installed as a per-tenant extension on your own BC environment (online SaaS or on-prem) — your data never routes through ECOSIRE servers
Built-in test/sandbox mode to validate flows against a BC sandbox company before going live
关于此产品
What this is
为什么选择 Power Automate / Zapier Integration Hub
Pre-built event triggers for BC business events (sales/purchase order released, customer/vendor created, item ledger posted, approval requested, payment registered) surfaced as clean Power Automate, Zapier and Make triggers
Record actions to create, update, find/upsert and delete BC entities (customers, items, sales orders, journal lines) callable from any of the three platforms
Ready-to-import connector templates and example flows for Power Automate, Zapier and Make so your team starts from a working blueprint, not a blank canvas
Outbound webhook publisher that fires signed JSON payloads to any HTTPS endpoint, with HMAC signature, retry-with-backoff and a dispatch log for replay
Field mapping and transform engine — map BC fields to target schemas with type casts, lookups, constants, conditional skips and value translation tables, configurable without redeploying code
Built on AL event subscribers, table/page extensions and bound API pages over the BC REST/OData v4 API for stable, upgrade-safe integration points
The Power Automate / Zapier Integration Hub is a custom-built AL extension for Microsoft Dynamics 365 Business Central that turns BC events and records into first-class automation primitives for Power Automate, Zapier and Make (Integromat). Instead of wiring brittle, one-off flows against raw OData endpoints, your ops team gets curated triggers (sales order released, customer created, item posted, approval requested, payment registered) and actions (create/update/find/delete records, run a posting routine, attach a document) that read like business verbs.
This is not an instant AppSource download. ECOSIRE scopes the exact tables, events and connectors you need, builds the extension, and installs it as a per-tenant extension directly on your Business Central environment (SaaS online or on-prem). We then configure the connectors, permission sets and ready-made flow templates with you.
How it works under the hood
The hub is built in AL using table extensions, page extensions and event subscribers that hook BC's published business events. Outbound automation is delivered through a webhook publisher that fires signed payloads to Power Automate / Zapier / Make endpoints, while inbound automation is served by bound API pages over the BC REST/OData v4 API and, where you use the Power Platform, native Dataverse virtual tables. A field mapping and transform layer lets you reshape BC fields into the schema each downstream app expects — type casts, lookups, default values and conditional skips — without code changes per flow.
Execution is throttled and retried through the Job Queue so bursts never overwhelm BC, and every dispatch is logged for replay. Security follows BC norms: dedicated permission sets, OAuth/Microsoft Entra app registrations, and least-privilege API access.
Honest delivery
You pay a one-time build fee. ECOSIRE delivers the working extension, installs it, hands over documentation, and supports it. Lead time and scope are agreed up front — no surprises, no rented monthly black box.
你得到什么
- A custom AL per-tenant extension (.app) built to your scoped triggers, actions and entities, installed on your Business Central environment
- Configured webhook publisher with signing secrets, endpoints and retry policy set for your target platforms
- Importable starter flow templates for Power Automate, Zapier and Make covering your priority use cases
- Field-mapping profiles configured for each integration, plus a setup page to maintain them
- Permission sets and a Microsoft Entra app registration guide for least-privilege OAuth access
- Technical documentation: trigger/action catalog, payload schemas, mapping reference and operations runbook
- A working sandbox validation pass plus go-live cutover support and a post-deployment support window
这是给谁的
Operations / RevOps Manager
Owns the cross-app workflows around BC and wants orders, customers and approvals to flow automatically into CRM, helpdesk and notification tools without begging IT for every new flow.
Business Central Functional Consultant / Admin
Maintains the BC tenant and needs an upgrade-safe, permission-scoped integration layer rather than ad-hoc OData hacks that break on the next BC update.
Power Platform / Automation Developer
Builds Power Automate, Zapier and Make flows and wants reliable, well-documented BC triggers and actions with signed webhooks and idempotency instead of polling raw API pages.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Power Automate / Zapier Integration Hub 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 Power Automate / Zapier Integration Hub，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
Power Automate / Zapier Integration Hub 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Curated business-event triggers (order released, approval requested) instead of raw API polling | 包含 | 部分支持 | 部分支持 | |
| Works across Power Automate, Zapier and Make with ready-made templates | 包含 | 部分支持 | 部分支持 | |
| Configurable field mapping & transform layer (no redeploy per flow) | 包含 | 不包括在内 | 部分支持 | |
| Signed outbound webhook publisher with retry, dead-letter and replay | 包含 | 部分支持 | 部分支持 | |
| Idempotency / duplicate-suppression on inbound record actions | 包含 | 部分支持 | 部分支持 | |
| Tailored to your exact tables, events and connectors | 包含 | 包含 | 不包括在内 | |
| Installed and supported on your tenant by the builder | 包含 | 部分支持 | 不包括在内 | |
| Upgrade-safe AL extension points (event subscribers, bound API pages) | 包含 | 部分支持 | 包含 | |
| No monthly platform rent for the integration layer itself | 包含 | 包含 | 不包括在内 |
关于Power Automate / Zapier Integration Hub的常见问题
How long does delivery take, and is this an AppSource app I can install instantly?
No — this is a build-to-order extension, not an instant AppSource download. After we scope the exact triggers, actions and entities you need, typical delivery is roughly 2 to 4 weeks depending on how many events, connectors and mapping profiles are in scope. ECOSIRE builds the AL extension, installs it as a per-tenant extension on your Business Central environment, configures the connectors and templates with you, and validates everything in a sandbox before go-live. The lead time is agreed in writing up front.
What happens with ongoing support and Business Central updates?
Your one-time build fee includes documentation, go-live support and a post-deployment support window. Because the extension is built on supported AL extension points (event subscribers, bound API pages, the REST/OData v4 API), it is designed to survive BC's monthly and major updates. We can verify it against each BC release and add new triggers, actions or mapping changes under a support or change-request arrangement — agreed before any work starts. You own the deployed extension on your tenant.
Does my data pass through ECOSIRE servers?
No. The hub is installed as a per-tenant extension on your own Business Central environment and the webhook publisher fires directly from BC to your chosen Power Automate, Zapier or Make endpoints. ECOSIRE builds and supports the extension but is not in the data path for your automations.
Can it connect to all three — Power Automate, Zapier and Make?
Yes. The webhook publisher and bound API pages are platform-neutral HTTPS/REST, so the same triggers and actions work with Power Automate, Zapier and Make. We provide importable starter templates for each platform you plan to use. If you run on the Microsoft stack we can also surface Dataverse virtual tables for tighter native Power Platform integration.
How do you stop retried flows from creating duplicate records in Business Central?
Inbound actions support idempotency keys and duplicate-suppression, so a retried or replayed flow updates the existing record instead of creating a second one. Outbound dispatches are logged with retry-and-backoff and a dead-letter view, so failed automations are visible and recoverable rather than silently lost or doubled.
相关模块
申请报价
Power Automate / Zapier Integration Hub
A per-tenant Business Central extension that exposes rich event triggers and create/update/find actions to Power Automate, Zapier and Make, with a built-in webhook publisher and field-mapping engine. Built, installed and supported by ECOSIRE on your BC environment.
- Pre-built event triggers for BC business events (sales/purchase order released, customer/vendor created, item ledger posted, approval requested, payment registered) surfaced as clean Power Automate, Zapier and Make triggers
- Record actions to create, update, find/upsert and delete BC entities (customers, items, sales orders, journal lines) callable from any of the three platforms
- Ready-to-import connector templates and example flows for Power Automate, Zapier and Make so your team starts from a working blueprint, not a blank canvas
- Outbound webhook publisher that fires signed JSON payloads to any HTTPS endpoint, with HMAC signature, retry-with-backoff and a dispatch log for replay