In Sytex, automations let you simplify your daily work by setting up flows that handle repetitive tasks or processes that need to run constantly on your behalf. This tool is designed to help you save time, avoid manual errors, and keep everything in order without any coding.
Imagine that every time a task is added to a Site, you always have to assign it to a responsible person and notify them by email. Instead of doing this manually, you can set up an automation that does it automatically whenever that situation occurs.
Sytex lets you create automated workflows that trigger when a specific event occurs, when a user presses a button, through an API call, or on a defined schedule. These actions can be simple—like changing a task's status—or more complex, like creating related objects, running scripts, querying external services with AI, or notifying different teams.
Automations work with a model: each automation is created once and can be reused across multiple contexts. You no longer need to duplicate the logic if you need the same flow in different templates or situations. If you change the logic, the change applies everywhere it's used.
A single automation can run from any of these contexts:
Runs when something happens in a form or task (e.g., "a form was approved", "a task was completed"). Set it up from the window.
Runs on events that apply at the general organization level, not tied to a specific template. It's also set up as a trigger.
A button visible to the user that runs the automation when clicked. Set it up from the window.
Runs externally through a call to the Sytex API. It can return a custom HTTP response.
An automation can run another as part of its steps.
Each automation can define —the data it needs to work (for example: a Site, a task, a text, a date). When you connect it to a trigger or a button, you configure where those parameter values come from in that context.
An automation can only be connected to a context if all of its required parameters can be provided from there. If any is left unassigned, the system flags it with a warning.
You can also create automations without parameters, for flows that don't need any input data.