Connectors
A connector is the component that handles authentication and communication with one specific external system. Every job in EZY Integrations has a source connector and a target connector. The connector you choose depends on the system you are connecting to, the direction data must flow, and the entity types you need to move. Before selecting a connector, review the architecture overview to understand how sources and targets fit into the pipeline, and the pipeline stages page to understand what happens to records after they leave the source connector.
Connector comparison
Section titled “Connector comparison”| Connector | Direction | Auth model | Headline entity types | Page |
|---|---|---|---|---|
| SAP Business One | Source + Target | SQL Server credentials; Service Layer URL + username/password for write-back; optional network credentials for file paths | Item, Business Partner, Price List, Sales Quotation, Sales Order | SAP B1 |
| EZY Portal | Source + Target | Portal URL + integration API key | Item, Business Partner, Price List, Sales Quotation, Sales Order | EZY Portal |
| Shopify | Source + Target | OAuth (Client ID + Client secret) or legacy access token, per-store | Item, Customer, Order | Shopify |
| WooCommerce | Source only | REST API consumer key + consumer secret; optional WordPress Application Password | Item, Customer, Order | WooCommerce |
| Wix | Source only | Wix API key + site ID | Customer, Order, Booking, Product, Service, Plan, Menu Item, Subscription | Wix |
| Flat File | Target only | Output directory path + format (CSV or XML) — no external authentication | Any entity type | Flat File |
| Generic API | Target only | None, API key, Bearer token, or HTTP Basic | Any entity type | Generic API |
Connector descriptions
Section titled “Connector descriptions”SAP Business One
Section titled “SAP Business One”The SAP Business One connector reads master data and transactional documents directly from the SAP B1 SQL Server database and writes sales quotations and orders back through the SAP Service Layer REST API. It is the most fully-featured connector, supporting eleven source entity types and bidirectional flow for sales documents. Incremental sync uses either the UpdateDate column or SQL Server Change Tracking. Use this connector whenever SAP B1 is your primary ERP and you need to synchronize master data, push documents, or both. Full details.
EZY Portal
Section titled “EZY Portal”The EZY Portal connector reads from and writes to the EZY Portal REST API using an integration API key. It is the most common target in a typical integration: SAP B1 or an e-commerce platform sends master data into Portal, and Portal sends sales documents back. It supports the full set of master data entity types — items, business partners, price lists, reference tables — plus bidirectional sales quotations and orders. Full details.
Shopify
Section titled “Shopify”The Shopify connector uses the Shopify GraphQL Admin API and supports both source and target directions. As a source it extracts products, customers, and orders. As a target it writes products (including variants, images, metafields, and inventory) back to Shopify. Authentication uses OAuth with a custom app’s Client ID and Client secret, or a legacy access token. A smart hash-based check skips unchanged records to reduce API quota consumption. Full details.
WooCommerce
Section titled “WooCommerce”The WooCommerce connector extracts products, customers, and orders from a WooCommerce store using the WooCommerce REST API v3 with a consumer key and consumer secret. It is source-only — data flows out of WooCommerce, not into it. Incremental sync uses a timestamp cursor on date_modified. An optional WordPress Application Password is required only when your mapping configuration performs media or file operations. Full details.
The Wix connector pulls data from Wix Studio sites using the Wix REST APIs and a Wix API key plus site ID. It is source-only and supports eight entity types, covering contacts, orders, bookings, products, services, pricing plans, menu items, and subscriptions. This breadth makes it suited for businesses that use Wix not just as an online store but also for bookings, restaurants, and subscription billing. Full details.
Flat File
Section titled “Flat File”The Flat File connector writes pipeline output to CSV or XML files on the server filesystem. It is target-only and accepts every entity type the platform supports. No external authentication is required — configuration consists of an output directory path and a format choice. Use it when the receiving system ingests data from files rather than a live API, or when you need an audit archive of every run. Full details.
Generic API
Section titled “Generic API”The Generic API connector delivers transformed records to any HTTP or REST endpoint. It is target-only, accepts every entity type, and supports four authentication modes: None, API key, Bearer token, and HTTP Basic. The request URL and HTTP method can be overridden per-record from within the mapping configuration. Use it to integrate with any system that accepts structured HTTP requests but does not have a dedicated connector. Full details.
Choosing a connector
Section titled “Choosing a connector”Use this guide to narrow your choice:
- Your ERP is SAP Business One — use the SAP Business One connector as the source and EZY Portal or Shopify as the target.
- You are populating a Portal tenant — use EZY Portal as the target, paired with SAP Business One, Shopify, WooCommerce, or Wix as the source.
- You sell on Shopify and need two-way sync — use Shopify as both source and target in separate jobs: one job pulls orders into Portal, another pushes the item catalog from Portal back to Shopify.
- You sell on WooCommerce — use WooCommerce as the source; it is extract-only, so pair it with EZY Portal, Flat File, or Generic API as the target.
- You use Wix for bookings, subscriptions, or a restaurant menu — use the Wix connector as the source to capture entity types beyond standard products and orders.
- The target system reads files — use Flat File as the target. Choose CSV or XML to match what the downstream system expects.
- The target system has an HTTP API but no dedicated connector — use Generic API as the target and configure authentication and the endpoint URL in the connection profile.
- You need a custom HTTP source — the Generic API connector is target-only; for an inbound HTTP push consider the API reference or contact support.
Related
Section titled “Related”- Credentials and Secrets — How connection profile credentials are stored and secured.
- Entity Types — Full list of entity types and the connectors that support each one.
- Mapping Configuration — How to configure field mappings for any connector pair.