Don't see your application listed here?
We can develop custom connectors for any application, protocol, or data source.
Submit Request
Hundreds of Connectors
Application & Data Connectors
Best-in-Class Connectivity. Drag & Drop Interface. Configure and Use in Minutes.
Core | MFT | EDI | Database | Integration
Try It Now Start the Product Tour
Core Connectors
The CData Arc Core framework includes several connectors that support a wide range of file transfer, database, data transformation, and workflow management capabilities.
Managed File Transfer Connectors
Arc MFT Connectors enable reliable, secure, and scalable managed file transfer across a wide range of messaging and file transfer protocols.
Database Connectors
Straightforward integration with popular databases, data warehouses, and other common data stores.
Application Connectors
Simplified access to enterprise applications like e-commerce platforms, CRM solutions, ERP systems, accounting applications, and more.
Adobe Commerce
Amazon Marketplace
AMQP
BigCommerce
Dynamics 365 Business Central
Databricks
DataRobot
Dynamics 365
Exact Online
FHIR
IBM MQ
SAP (IDoc)
Infor
Apache Kafka
MQTT
NetSuite
Odoo
Payment
QuickBooks Online
Sage Intacct
Salesforce
ShipStation
Shopify
Snowflake
Square
Stripe
Tally
WooCommerce
Zoho CRM
Zoho Inventory
Sample Flows
A Library of Pre-Packaged Integration Flows Connecting Your Apps and Trading Partners.
Logistics & Supply Chain Flows
The following flows demonstrate EDI integration for logistics documents like Load Tenders, Shipment Status Updates, and more.
EDI 210 (Load Tender Invoice) to CSV
Receive 210s from your trading partner and convert the data into a CSV flat file format for further processing.
SQL Server to EDI 214 (Shipment Status Update)
Generate outbound 214s from data contained in a SQL Server back-end system.
SQL Server to EDI 204 (Load Tender)
Generate outbound 204s from data contained in a SQL Server back-end system.
MySQL to EDI 214 (Shipment Status Update)
Generate outbound 214s from data contained in a MySQL back-end system.
MySQL to EDI 204 (Load Tender)
Generate outbound 204s from data contained in a MySQL back-end system.
CSV to EDI 214 (Shipment Status Update)
Generate outbound 214s from data contained in CSV flat files.
CSV to EDI 204 (Load Tender)
Generate outbound 204s from data contained in CSV flat files.
EDI 210 (Load Tender Invoice) to SQL Server
Receive 210s from your trading partner and integrate the data into a SQL Server back-end.
EDI 210 (Load Tender Invoice) to MySQL
Receive 210s from your trading partner and integrate the data into a MySQL back-end.
SQL Server to EDI 856 (Advanced Shipment Notice)
Generate outbound 856s from data contained in a SQL Server back-end system.
Retail & E-Commerce Flows
The following flows demonstrate EDI integration for retail documents and order integrations for e-commerce platforms.
SQL Server to EDI 846 (Inventory Inquiry)
Generate outbound 846s from data contained in a SQL Server back-end.
Shopify to SQL Server
Retrieve order data from Shopify's web storefront and store that data in a SQL Server back-end system.
Shopify to MySQL
Retrieve order data from Shopify's web storefront and store that data in a MySQL back-end system.
Shopify to CSV
Retrieve order data from Shopify's web storefront and store that data as a CSV file.
Oracle to EDI 856 (Advance Shipment Notice)
Generate outbound 856s from data contained in a Oracle back-end system.
NetSuite to EDI 846 (Inventory Inquiry)
Generate outbound 846s using data pulled from your NetSuite back-end.
MySQL to EDI 856 (Advanced Shipment Notice)
Generate outbound 856s from data contained in a MySQL back-end system.
MySQL to EDI 846 (Inventory Inquiry)
Generate outbound 846s from data contained in a MySQL back-end system.
Healthcare Flows
The following flows demonstrate EDI integration for healthcare documents like Healthcare Claims, Benefit Enrollments, and more.
SQL Server to EDI 837 (Healthcare Claim)
Generate outbound 837s from data contained in a SQL Server back-end.
SQL Server to EDI 834 (Benefit Enrollment)
Generate outbound 834s from data contained in a SQL Server back-end.
MySQL to EDI 837 (Healthcare Claim)
Generate outbound 837s from data contained in a MySQL back-end system.
CSV to EDI 837 (Healthcare Claim)
Generate outbound 837s from data contained in CSV flat files.
CSV to EDI 834 (Benefit Enrollment)
Generate outbound 834s from data contained in CSV flat files.
Suppliers & Manufacturers Flows
The following flows demonstrate EDI integration for suppliers & manufacturers, using documents like inbound Purchase Orders, outbound Invoices, and more.
SQL Server to EDI 810 (Invoice)
Generate outbound 810s from data contained in a SQL Server back-end system.
Oracle to EDI 810 (Invoice)
Generate outbound 810s from data contained in a Oracle back-end system.
NetSuite to EDI 810 (Invoice)
Generate outbound 810s using data pulled from your NetSuite back-end.
SQL Server to EDI 855 (Purchase Order Acknowledgment)
Generate outbound 855s from data contained in a SQL Server back-end system.
MySQL to EDI 855 (Purchase Order Acknowledgment)
Generate outbound 855s from data contained in a MySQL back-end system.
MySQL to EDI 810 (Invoice)
Generate outbound 810s from data contained in a MySQL back-end system.
EDI 850 (Purchase Order) to SQL Server
Receive 850s from your trading partner and integrate the data into a SQL Server back-end.
EDI 850 (Purchase Order) to Oracle
Receive 850s from your trading partner and integrate the data into a Oracle back-end.
EDI 850 (Purchase Order) to NetSuite
Receive 850s from your trading partner and integrate the data into a NetSuite back-end.
EDI 850 (Purchase Order) to MySQL
Receive 850s from your trading partner and integrate the data into a MySQL back-end.
Sample Flows
A Library of Pre-Packaged Integration Flows Connecting Your Apps and Trading Partners.
Logistics & Supply Chain Flows
The following flows demonstrate EDI integration for logistics documents like Load Tenders, Shipment Status Updates, and more.
EDI 210 (Load Tender Invoice) to CSV
Receive 210s from your trading partner and convert the data into a CSV flat file format for further processing.
SQL Server to EDI 214 (Shipment Status Update)
Generate outbound 214s from data contained in a SQL Server back-end system.
SQL Server to EDI 204 (Load Tender)
Generate outbound 204s from data contained in a SQL Server back-end system.
MySQL to EDI 214 (Shipment Status Update)
Generate outbound 214s from data contained in a MySQL back-end system.
MySQL to EDI 204 (Load Tender)
Generate outbound 204s from data contained in a MySQL back-end system.
CSV to EDI 214 (Shipment Status Update)
Generate outbound 214s from data contained in CSV flat files.
CSV to EDI 204 (Load Tender)
Generate outbound 204s from data contained in CSV flat files.
EDI 210 (Load Tender Invoice) to SQL Server
Receive 210s from your trading partner and integrate the data into a SQL Server back-end.
EDI 210 (Load Tender Invoice) to MySQL
Receive 210s from your trading partner and integrate the data into a MySQL back-end.
SQL Server to EDI 856 (Advanced Shipment Notice)
Generate outbound 856s from data contained in a SQL Server back-end system.
Retail & E-Commerce Flows
The following flows demonstrate EDI integration for retail documents and order integrations for e-commerce platforms.
SQL Server to EDI 846 (Inventory Inquiry)
Generate outbound 846s from data contained in a SQL Server back-end.
Shopify to SQL Server
Retrieve order data from Shopify's web storefront and store that data in a SQL Server back-end system.
Shopify to MySQL
Retrieve order data from Shopify's web storefront and store that data in a MySQL back-end system.
Shopify to CSV
Retrieve order data from Shopify's web storefront and store that data as a CSV file.
Oracle to EDI 856 (Advance Shipment Notice)
Generate outbound 856s from data contained in a Oracle back-end system.
NetSuite to EDI 846 (Inventory Inquiry)
Generate outbound 846s using data pulled from your NetSuite back-end.
MySQL to EDI 856 (Advanced Shipment Notice)
Generate outbound 856s from data contained in a MySQL back-end system.
MySQL to EDI 846 (Inventory Inquiry)
Generate outbound 846s from data contained in a MySQL back-end system.
Healthcare Flows
The following flows demonstrate EDI integration for healthcare documents like Healthcare Claims, Benefit Enrollments, and more.
SQL Server to EDI 837 (Healthcare Claim)
Generate outbound 837s from data contained in a SQL Server back-end.
SQL Server to EDI 834 (Benefit Enrollment)
Generate outbound 834s from data contained in a SQL Server back-end.
MySQL to EDI 837 (Healthcare Claim)
Generate outbound 837s from data contained in a MySQL back-end system.
CSV to EDI 837 (Healthcare Claim)
Generate outbound 837s from data contained in CSV flat files.
CSV to EDI 834 (Benefit Enrollment)
Generate outbound 834s from data contained in CSV flat files.
Suppliers & Manufacturers Flows
The following flows demonstrate EDI integration for suppliers & manufacturers, using documents like inbound Purchase Orders, outbound Invoices, and more.
SQL Server to EDI 810 (Invoice)
Generate outbound 810s from data contained in a SQL Server back-end system.
Oracle to EDI 810 (Invoice)
Generate outbound 810s from data contained in a Oracle back-end system.
NetSuite to EDI 810 (Invoice)
Generate outbound 810s using data pulled from your NetSuite back-end.
SQL Server to EDI 855 (Purchase Order Acknowledgment)
Generate outbound 855s from data contained in a SQL Server back-end system.
MySQL to EDI 855 (Purchase Order Acknowledgment)
Generate outbound 855s from data contained in a MySQL back-end system.
MySQL to EDI 810 (Invoice)
Generate outbound 810s from data contained in a MySQL back-end system.
EDI 850 (Purchase Order) to SQL Server
Receive 850s from your trading partner and integrate the data into a SQL Server back-end.
EDI 850 (Purchase Order) to Oracle
Receive 850s from your trading partner and integrate the data into a Oracle back-end.
EDI 850 (Purchase Order) to NetSuite
Receive 850s from your trading partner and integrate the data into a NetSuite back-end.
EDI 850 (Purchase Order) to MySQL
Receive 850s from your trading partner and integrate the data into a MySQL back-end.
Submit Request