Database

SQL Server Integration

Zynk's SQL Server integration lets workflows read from and write to Microsoft SQL Server databases using your own T-SQL. Select queries pull rows out for Sage, Shopify, Business Central or Salesforce, while other tasks insert or update tables, return single values and loop through results. It suits teams running in-house systems, product masters or reporting databases on SQL Server.

Available for

Workflow

Capabilities may differ depending on the product.

See what you can do Book a call →

Benefits

Why businesses connect SQL Server

Your queries, your schema

Workflows run the T-SQL you write against your own tables and views, so Zynk works with the way your database is already structured instead of asking you to reshape data into a fixed import format first.

Structured XML from the query

The XML select task works with queries that use SQL Server's FOR XML clause. One statement can return order headers with their lines already nested, which cuts down the mapping needed before the data is imported elsewhere.

Row by row when you need it

The MS SQL Repeater steps through query results one row at a time and runs further tasks for each, for example creating a sales order per row and then writing the new document number back to your table.

Quick lookups and checks

Scalar queries return a single value, such as a count, a last-run date or an account code. Workflows use that value to decide what to fetch next, or to finish early when there is nothing new to send.

Reporting tables kept current

Data exported from accounting, ERP and ecommerce connectors can be written into SQL Server on a schedule, so reports and BI tools draw on recent figures without anyone running exports and imports by hand.

Runs where your database lives

Zynk Workflow can be deployed on-premise or in the cloud. That means it can run on your own network, next to a SQL Server instance you would rather keep internal, and still reach the cloud systems it exchanges data with.

Capabilities

What you can do with SQL Server

Every task the Zynk SQL Server connector can run, grouped by the direction data moves.

Actions in SQL Server

Tasks Zynk can automate in SQL Server

5 tasks

Execute query → in SQL Server
Execute scalar query → in SQL Server
Execute select query → in SQL Server
Execute XML select query → in SQL Server
MS SQL repeater → in SQL Server

Need something that isn't listed?

Most SQL Server projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate SQL Server?

SQL Server often holds the data that matters most: a bespoke order system, a product master or the reporting warehouse. Moving that data into Sage or an online store usually relies on exports, scripts written years ago or one busy developer. When a script breaks, nobody notices until a customer or the finance team does.

Without integration

Nightly CSV exports from SQL Server reimported into Sage by hand
Custom scripts that only one developer understands
Reporting tables that lag a week behind the accounts
A failed overnight script that goes unnoticed for days
Web orders copied into the in-house system line by line

With Zynk

Select queries feed Sage directly on a schedule
Low-code workflows the wider team can read and adjust
Accounting and order data written to SQL Server on every scheduled run
Alerts raised when a query or import fails
Orders inserted into your own tables automatically

How it works

How the SQL Server integration works

Step 1: Connect to the database
Zynk Workflow connects to your SQL Server instance using a database login that you control. Grant it only the tables, views and procedures the integration actually needs.
Step 2: Write the queries
Select, scalar and XML select queries define what leaves the database. Execute queries define what is written back, such as inserting orders or flagging rows as sent.
Step 3: Map to the other system
Query results are mapped to the fields of Sage, Business Central, Shopify or whichever connector sits on the other side, with transformations for codes, dates and tax.
Step 4: Schedule and monitor
The workflow runs on a timetable you set. Rows are marked as processed only once they succeed, so anything that failed is picked up again on the next run rather than lost.

Integrations

What can you connect to SQL Server?

Sage 200

Shopify

Microsoft Dynamics 365 Business Central

Example use cases for SQL Server integration

SQL Server and Sage 200

Take orders captured by an in-house system on SQL Server into Sage 200 as sales orders, and write Sage 200 sales transactions and stock records back into your own tables for reporting.

Sales ordersSales transactions, Stock records

View the Sage 200 integration →

SQL Server and Shopify

Keep Shopify products and stock in line with a product database held in SQL Server, and land every new Shopify order in your own tables for fulfilment or analysis.

Products, InventoryOrders

View the Shopify integration →

SQL Server and Microsoft Dynamics 365 Business Central

Copy Business Central customers and posted sales invoices into SQL Server for reporting, and post journals to Business Central from figures calculated in the database.

JournalsCustomers, Sales invoices

View the Microsoft Dynamics 365 Business Central integration →

SQL Server and Salesforce

Publish products and prices from a SQL Server product master to Salesforce, so price books match the catalogue that your other systems read from.

Products, Prices

View the Salesforce integration →

SQL Server and Xero

Pull Xero invoices and payments into SQL Server tables on a schedule, so finance reporting can join accounting data with figures from the rest of the business.

Invoices, Payments

View the Xero integration →

Find your integration →

SQL Server integration FAQs

How do I get data from SQL Server into Sage 200?

Zynk runs a select query against your SQL Server tables and maps the rows to a Sage 200 import, such as sales orders or customers. Once the import succeeds, an execute query can mark those rows as processed, so the next run only picks up new records.

What is the MS SQL Repeater task?

It is a Zynk Workflow task that runs a query and then repeats a set of child tasks for every row returned. It suits jobs where each row needs its own action, such as creating one document per row or calling another system once per customer.

Can Zynk write data into SQL Server?

Yes. The execute query task runs statements that change data, such as inserts, updates or deletes, using values mapped from another system. That is how orders, invoices or stock figures exported by other connectors end up in your own tables.

Does the SQL Server connector work with an on-premise database?

Yes. Zynk Workflow can be deployed on-premise or in the cloud. For a database on your internal network, the workflow can run on a machine that reaches the SQL Server instance directly, so the database can stay inside your network.

Do I need a developer to use the SQL Server connector?

You need someone comfortable writing T-SQL, because the queries run against your schema. Mapping, scheduling and error handling are set up in Zynk's low-code designer, and our team can help write or review the queries during the project.

What does the XML select query task do?

It runs a query that builds its own XML through SQL Server's FOR XML clause. Because the database shapes the output, header and line data can arrive already nested, which reduces the mapping needed before the data is imported into another system.

Which systems can SQL Server data reach through Zynk?

Any system with a Zynk connector, including Sage 50, Sage 200, Business Central, Xero, Shopify, Magento and Salesforce. The SQL Server tasks handle the database side, and the other connector's own import and export tasks handle the rest.

See what Zynk can automate for your SQL Server setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a call See pricing →