Other
User Interface Integration
Zynk's User Interface connector adds on-screen interaction to Zynk Workflow. Message boxes, input boxes, informational log messages and a view of the last task's output let a person confirm, enter or check data while a workflow runs. It suits integrations that are started by hand, such as a month-end export from Sage, and teams building or testing new workflows.
Capabilities may differ depending on the product.
Benefits
Why businesses connect User Interface
Approval before anything is posted
A message box with Yes and No, or OK and Cancel, buttons can pause a workflow before a critical step. Sub-tasks run only for the answer you specify, so a batch of journals or invoices is posted only once someone agrees.
Ask for the values a run needs
An input box asks the operator for a date, number, piece of text or file, then passes it to the next task or stores it in a workflow variable. A period end date or a single order reference are good examples.
Entries checked as they are typed
Input conditions test the value before the workflow continues: ranges for numbers and dates, regular expressions for text and patterns for file names. If an entry fails, the user sees an error and can try again.
Quicker debugging
Display Last Output shows what the previous task produced, and a message box can display a variable or file. While building a workflow you can check the data at each step instead of opening output files afterwards.
Predictable when nobody is watching
Every message box has a default answer for when Zynk is running in the background and cannot show it on screen. One workflow can therefore be started by hand during the day and still run safely on a schedule.
Progress people can follow
Log Info Message writes informational messages as the workflow runs, so whoever started it can see which stage has finished and what was processed, rather than wondering whether a long run has stalled.
Capabilities
What you can do with User Interface
Every task the Zynk User Interface connector can run, grouped by the direction data moves.
Actions in User Interface
Tasks Zynk can automate in User Interface
4 tasks
- Display last output → in User Interface
- Input box → in User Interface
- Log info message → in User Interface
- Message box → in User Interface
Need something that isn't listed?
Most User Interface projects include at least one custom step. Our team builds it for you.
The problem
Why integrate User Interface?
Many Zynk workflows run unattended, which suits routine order and stock updates. Some processes still need a person: a month-end export that needs a date, a batch that should be checked before it posts, or a new workflow under test. Without interactive steps, those decisions happen outside the workflow, in emails, notes or hand-edited files.
Without integration
- Settings edited by hand to change a date range before each run
- Large batches posted before anyone has looked at them
- Typos in a reference that only surface after the import fails
- Output files opened one by one to see what a task produced
- Users unsure whether a long run is still working
With Zynk
- An input box asks for the date range when the workflow starts
- A Yes or No message box confirms the batch before it posts
- Input conditions reject invalid entries straight away
- Display Last Output shows the result on screen
- Log Info Message reports progress as each stage completes
How it works
How the User Interface integration works
Step 1: Find where a person adds value
Identify the points in a workflow that need a decision or a value, such as choosing a period, approving a batch or confirming a file before it is processed.
Step 2: Add the interface tasks
Place a message box, input box, log message or Display Last Output task in the workflow using Zynk's low-code designer, then set captions, buttons, input types and any conditions.
Step 3: Branch on the answer
Put the tasks that should only run after approval inside the message box as sub-tasks, or feed the input box value into the next task or a workflow variable used later on.
Step 4: Set an unattended default
Choose the default answer each message box gives when Zynk runs in the background, so the workflow behaves the same way on a schedule as it does when started manually.
Integrations
What can you connect to User Interface?
Example use cases for User Interface integration
User Interface and Sage 50 UK
Prompt for a period end date with an input box before transactions are exported from Sage 50, then show a message box so the user confirms the output before it is sent on.
User Interface and Sage 200
Show a Yes or No message box before a batch of purchase invoices is imported into Sage 200, so a finance user signs off each run before anything reaches the ledger.
User Interface and Xero
Ask for a date range before invoices are exported from Xero to another system, and write log messages as the run progresses so the user can see it complete.
User Interface and Shopify
Use Display Last Output while testing a Shopify order workflow to check what each step returned, before the workflow is handed over to run on a schedule.
User Interface integration FAQs
What is the User Interface connector for?
Can a Zynk workflow ask for approval before posting data?
What happens to a message box when the workflow runs on a schedule?
What can the input box ask for?
Can the input box validate what users type?
Is the User Interface connector useful for testing workflows?
Which Zynk product includes the User Interface tasks?
See what Zynk can automate for your User Interface 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 →