No. This is a build-to-order product. ECOSIRE builds the Ecosire_ZapierMakeConnector module, configures your Zapier/Make triggers and actions, and installs it directly on your Magento 2 Open Source or Adobe Commerce environment. There is no Marketplace download link — you receive a connector tuned to your store, plus installation and support.

Typical delivery is 5–10 business days from the kickoff call, depending on how many custom triggers and actions you need and whether custom attributes or third-party extension entities are involved. We confirm a firm timeline after a short scoping session and install on staging first, then move to UAT and production cutover.

Every build includes a warranty window covering bug fixes and adjustments after handover. Because the module lives in your app/code, it survives Magento minor upgrades; we offer ongoing support plans for Magento version upgrades, new triggers/actions, and Zapier/Make platform changes. Support requests are handled by ECOSIRE directly.

Yes. The connector is built on standard Magento 2 mechanisms — events/observers, service contracts, REST/GraphQL, integration tokens, and admin ACL — that exist in both editions. On Adobe Commerce we can additionally account for B2B, shared catalogs, and multi-source inventory entities where relevant to your workflows.

Access is granted through scoped Magento integration tokens, never your admin password, and every endpoint is gated by a dedicated admin ACL resource (Ecosire_ZapierMakeConnector::config). Tokens are least-privilege and revocable, payloads can be filtered by store/status/customer group, and all webhook deliveries are logged for audit. We follow Magento security best practices and never use raw SQL.

Yes — that is the main advantage of build-to-order. We map your real EAV attributes, custom order/customer/product fields, and entities added by third-party extensions into the trigger and action payloads, rather than forcing you into a fixed off-the-shelf schema.