Automations

In Sytex, automations let you simplify daily work by setting up flows that handle repetitive tasks or processes that need to run consistently. This tool is designed to help you save time, avoid manual errors, and keep everything in order without needing to code.

What changed?

Automations now work with a single model: Standalone. This means each automation is created once and can be reused across multiple contexts. There is no longer a need to duplicate logic if you need the same flow in different templates or situations.

How can an automation be triggered?

A single automation can be executed from any of these contexts:
Trigger method
Description
Template event
Runs when something happens in a form or task (e.g., "form approved", "task completed"). Configured in the Triggers window.
Global event
Runs on events that apply at the organization level, not tied to a specific template. Also configured as a trigger.
Button in task or form
A visible button that runs the automation when clicked. Configured in the Actions window.
HTTP call (API)
Executed externally via a call to the Sytex API.
From another automation
An automation can execute another one as part of its steps.

Input parameters

Each automation can define input parameters — the data it needs to run (for example: a site, a task, a text, a date). When connecting it to a trigger or button, you configure where the values for those parameters come from in that context.
An automation can only be connected to a context if all its required parameters can be provided from there. If any parameter is left unassigned, the system shows a warning.
It is also possible to create automations without parameters, for flows that do not need input data.

Reusability

This is the main advantage of the new model. Previously, if you needed the same logic in two different templates, you had to duplicate the automation. Now you create it once and connect it to all the templates, events, or buttons you need. If you change the logic, the change applies everywhere it is used.

Management

Automations, their triggers, and their actions are managed from dedicated windows:
  • Automations: List and editor. Here you define the logic (steps, actions, input parameters).
  • Triggers: Connections between automations and events. Configure which automation fires on which event and how parameters are mapped.
  • Actions: Connections between automations and buttons. Configure which automation runs from which button, with what visible text, and how parameters are mapped.