Skip to main content

Feature in Focus: Integration Jobs With Workflow

Laptop featuring an integration jobs workflow

Overhaul your traditional method for creating integrations with automated workflows that free you from ongoing maintenance.

Unqork’s very own Jo Zeng (Product Manager) and Dom Piganell (Senior Engineer) hosted a webinar to demonstrate a critical feature in the Unqork platform: Building integration jobs with workflows.

Request a demo banner

Typically, an engineer would have to acquire the server, write custom software, write the bash script, and then maintain that server (e.g., handle OS upgrades and patches, network/firewall rules, etc.). This requires a slew of teams just to get started—Systems Admin, Networks Admin, Engineering, Security—creating roadblocks with both process and budget restraints.

It’s clear that the traditional method for creating workflow integrations is manual and time-consuming, requiring a lot of ad hoc maintenance. With the power of no-code, this can now be automated with a few clicks of a button!

Watch the build and learn about its use cases.

Automatically Trigger Workflows

Cron jobs help you schedule and run certain tasks on your server, automating tasks that run in the background periodically. Unqork set out to build something in Workflow that would imitate this. Rather than trigger workflows by user action, Unqork Creators can automate workflows with timers (Timer Start Nodes) or those that are triggered by internal signals (Signal Start Nodes). 

Example of signal start node trigger on laptopAn example of a Signal Start Node trigger.

Automated triggers provide many process benefits, including:

  • Reduced maintenance: No server maintenance, library upgrades, or firewall rules to maintain

  • Increased usability: Both technical and non-technical Creators can now set up an integration job, which would otherwise require years of training and experience. Integrations are maintained by Unqork, creating less overhead and reduced burden on the non-technical Creator.

  • Fewer resources: Does not require three or four tech teams just to maintain a single cron job

Workflow lets Creators “set it and forget it,” enabling them to focus on more pressing work while these cron jobs build integrations on the backend.