Database
SQLite Integration
Zynk's SQLite integration reads and updates SQLite database files inside a Zynk workflow. Select and scalar queries take data out of the file for Sage 50, Xero, QuickBooks or WooCommerce, execute queries write results back in, and a repeater handles records one at a time. It suits businesses whose apps, devices or internal tools keep their data in a local SQLite file.
Capabilities may differ depending on the product.
Benefits
Why businesses connect SQLite
No database server to manage
SQLite holds a complete database in one file with no separate server process. Zynk queries that file directly, so data kept by a desktop tool or line-of-business app can join your integrations without a migration project.
Use data your apps already keep
Plenty of software stores its records in SQLite behind the scenes. If the workflow can reach the file, it can read jobs, sales or stock counts from it and pass them to the systems your finance team relies on.
Results written back to the file
Execute queries insert or update rows in the SQLite file, for instance storing the invoice number Xero assigned or flagging a record as exported. The file itself then shows what has already been processed.
One record at a time
The SQLite Repeater runs a query and then performs the same set of tasks for each row returned. That suits jobs such as raising one invoice per completed job or creating one customer for each new record.
Simple checks before each run
A scalar query returns one value, such as how many rows are waiting or the date of the last export. The workflow can use it to skip a run when nothing has changed, or to decide which data to fetch.
Capabilities
What you can do with SQLite
Every task the Zynk SQLite connector can run, grouped by the direction data moves.
Actions in SQLite
Tasks Zynk can automate in SQLite
4 tasks
- Execute query → in SQLite
- Execute scalar query → in SQLite
- Execute select query → in SQLite
- SQLite repeater → in SQLite
Need something that isn't listed?
Most SQLite projects include at least one custom step. Our team builds it for you.
The problem
Why integrate SQLite?
SQLite turns up in more places than most teams realise: inside desktop software, handheld devices, data collection tools and small internal apps. The data it holds is useful to finance and operations, yet it rarely leaves the file unless someone opens a database browser, exports a CSV and retypes the results into the accounts.
Without integration
- Records exported from a SQLite file into spreadsheets before every month-end
- Jobs or sales logged in a local app and rekeyed into Sage 50
- No reliable record of which rows have already been sent
- Customer and item lists in the app drifting away from the accounts
- One-off scripts written just to pull data out of a single app
With Zynk
- Queries read the file and feed the accounts on a schedule
- Rows become transactions in Sage 50 without retyping
- Processed rows are flagged in the file by an execute query
- Customer and item lists are written into the file from accounting
- A low-code workflow that can be adjusted when the app changes
How it works
How the SQLite integration works
Step 1: Point Zynk at the file
Zynk Workflow is given the path to the SQLite database. Because SQLite keeps everything in that file, there is no server address, port or database service to set up.
Step 2: Query the data you need
Select queries define which tables and rows leave the file, and scalar queries supply single values for checks. Joins and filters run inside SQLite before anything reaches the next step.
Step 3: Map and deliver
Results are mapped to the target connector, such as Sage 50 invoices or QuickBooks sales receipts, with codes, dates and tax converted along the way.
Step 4: Record what happened
After each successful import, execute queries write references or status flags back into the file, so the following run only collects rows that have not been sent yet.
Integrations
What can you connect to SQLite?
Example use cases for SQLite integration
SQLite and Sage 50 UK
Turn rows recorded by a local SQLite application into Sage 50 invoices, and write Sage 50 customer and stock records into the file so the app works from current accounts data.
SQLite and QuickBooks
Post sales captured in a SQLite file to QuickBooks as sales receipts, and copy QuickBooks customers and items into the file so the app can look them up.
SQLite and Xero
Create Xero invoices from records in a SQLite database, then write Xero's payment details back so the file shows which invoices have been settled.
SQLite and WooCommerce
Load WooCommerce orders into a SQLite file used by a packing or reporting tool, and update WooCommerce products from the item data that file holds.
SQLite integration FAQs
Can Zynk read a SQLite database file?
Does SQLite need a database server for Zynk to connect?
Can Zynk update data in a SQLite file?
What is the SQLite Repeater?
What sort of software stores its data in SQLite?
Should I use the SQLite or SQL Server connector?
What information do you need to scope a SQLite project?
See what Zynk can automate for your SQLite 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 callSee pricing →