Other
Zynk Integration
The Zynk integration is the set of core tasks built into Zynk Workflow itself. They don't connect to an outside system; they control how a workflow runs. Integration teams use them to branch on conditions, start and stop workflows, track which records have already been processed, maintain mappings and render files, alongside connectors for Sage, Shopify, Xero and the rest.
Capabilities may differ depending on the product.
Benefits
Why businesses connect Zynk
Decisions inside a workflow
If Input Contains, If Input Equals, Else and Switch tasks send a workflow down different paths. Switch acts on the previous task's result, such as success with data, success with no data, not found or a failure.
No duplicate imports
The truth table records what Zynk has imported, holding each record's ID in both systems. Imports into Sage fill it automatically, and the truth record tasks let any workflow check, add, update or remove entries.
Mappings you can maintain
Upsert Mappings creates or updates Zynk's value mappings from XML, and If Mapping Exists checks for an entry before a record moves on. Lookups such as product codes or tax codes stay current without editing the workflow.
Files in any text format
Razor Template uses Microsoft's Razor engine to render text output, such as CSV, XML or HTML, from workflow data and variables. Zynk CSV to Zynk XML and Auto Mapper bring data into Zynk's own XML format.
Control over when work runs
Start Workflow chains one workflow into another, Stop Workflow ends a run early and Stop Repeater halts a loop at the current record. Check Internet Connection runs its sub-tasks only when an internet connection is, or isn't, available.
Reports when something needs attention
Set Error Flag marks a run as needing attention, which controls when a workflow report is generated and emailed. Create Backup saves all workflows and data to a zip file, timestamped if you want to keep several copies.
Capabilities
What you can do with Zynk
Every task the Zynk Zynk connector can run, grouped by the direction data moves.
Import into Zynk
Data Zynk writes into Zynk
1 task
- Cache records → into Zynk
Export out of Zynk
Data Zynk reads out of Zynk
1 task
- Truth records → out of Zynk
Actions in Zynk
Tasks Zynk can automate in Zynk
24 tasks
- Auto mapper → in Zynk
- Check internet connection → in Zynk
- Container task → in Zynk
- Create backup → in Zynk
- Dashboard loop → in Zynk
- Delete truth record → in Zynk
- Else task → in Zynk
- If input contains → in Zynk
- If input equals → in Zynk
- If mapping exists → in Zynk
- If truth record exists → in Zynk
- Insert truth record → in Zynk
- Razor template → in Zynk
- Set error flag → in Zynk
- Set variable → in Zynk
- Start process → in Zynk
- Start workflow → in Zynk
- Stop repeater → in Zynk
- Stop workflow → in Zynk
- Switch task → in Zynk
- Update truth record → in Zynk
- Upsert mappings → in Zynk
- Upsert truth records → in Zynk
- Zynk CSV to zynk XML → in Zynk
Need something that isn't listed?
Most Zynk projects include at least one custom step. Our team builds it for you.
The problem
Why integrate Zynk?
Moving data between two systems is rarely a straight line. Some records should be skipped, some need a lookup first, and a failed step should stop the run rather than leave half an order behind. Without control tasks, those rules end up in scripts outside the integration, where they are hard to see and harder to change.
Without integration
- Orders imported twice after a workflow is rerun
- Lookup tables kept in spreadsheets and copied into scripts
- Every step running even when an earlier one returned nothing
- Failures noticed days later when a customer complains
- Long processes crammed into one unreadable workflow
With Zynk
- Truth records show what has already been processed
- Mappings held in Zynk and updated by a task
- Switch and If tasks route the workflow by result
- Error flags decide when a workflow report is emailed
- Container tasks and Start Workflow split work into clear stages
How it works
How the Zynk integration works
Step 1: Group the steps
Container tasks hold related steps together, and Start Workflow hands over to the next workflow when a process needs more stages than one workflow comfortably holds.
Step 2: Add the rules
Conditional tasks test the input, a mapping or a truth record and run their sub-tasks only when the test passes. Set Variable stores values that later tasks read, such as a run date or a batch reference.
Step 3: Track what has run
Truth record tasks link each record's ID in one system with its ID in the other. Later runs check that link to skip records already sent, or to update them rather than create them again.
Step 4: Report and protect
Set Error Flag decides when a run is reported by email, and Create Backup keeps a copy of workflows and data, which makes moving Zynk to a replacement machine straightforward.
Integrations
What can you connect to Zynk?
Example use cases for Zynk integration
Zynk and Sage 50 UK
With duplicate prevention switched on, each order imported into Sage 50 gets a truth record. When the workflow runs again, orders already in the ledger are skipped and written to the fail file instead.
Zynk and Email
Set Error Flag inside an If task decides when a run counts as failed, and the Email connector's integration report then tells your team what needs attention.
Zynk and Shopify
Truth records hold the Shopify order ID against the ID created in your back office. If Truth Record Exists then decides whether an incoming order is new or an update to one already sent.
Zynk integration FAQs
What is the Zynk connector?
What are truth records in Zynk?
How do I stop a workflow importing the same order twice?
Can one Zynk workflow start another?
What does the Razor Template task do?
Can a Zynk workflow run an external program?
How do I know when a Zynk workflow fails?
Do I need to be a developer to use these tasks?
See what Zynk can automate for your Zynk 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 →