Automations

Workflow list

Every automation in your organisation, with a clear view of which are active and which recently failed. Up to five active workflows with the Starter licence, as many as you like with Securo Automation Pro.

Workflow editor

One trigger and one action per workflow: pick, fill in, test, activate. Recipients are found by name, module actions are filled in as a form — assembled by clicking rather than programming.

Module events as triggers

A new employee, a deal won, a contract created, a working-time breach — the hub itself gives the starting signal. Workflows can also be started at the push of a button.

Schedule

Every few minutes, hourly, daily, weekly or monthly — at the chosen time in your time zone, across daylight saving changes too. “Next runs” shows in advance when it will run.

Actions across modules

Notify one person, several people or the whole organisation, run a module action such as “Create customer” or “Create letter from template”, wait up to seven days or start another workflow.

Loop for each element

Run an action for every element of a list from the event — up to 1,000 runs, up to ten at the same time. With “Continue on errors” the loop finishes despite individual failures.

AI request as a step

An instruction to a model your organisation has approved — optionally with the answer as structured data; if it cannot be read, the step fails visibly. With Securo AI.

Values from the trigger

With “Insert variable” you take values from the event — such as a new employee's first name — into title, text or details. During the run the real value appears there.

Ready-made templates

HR onboarding, new CRM customer, critical incident, working-time breach — adopt, adjust in the editor, activate.

Start from outside

Trigger workflows from a third-party system — secured by signature or token, with a secret you can renew at any time, and pausable when needed. With Securo Automation Pro.

Request to another system

Inside a loop, a workflow calls an external system — with address, credentials, additional headers, values sent and a time limit. Secrets are masked in the run.

Encrypted credentials

Tokens for external systems are stored encrypted; the plain text is never shown again. Renewing swaps only the secret, and workflows keep running unchanged. With Securo Automation Pro.

Runs

Every execution, newest first — you see immediately what worked and what did not.

Step-by-step inspector

Each step with status, duration, input and result. A run can be repeated with the same workflow version; if that could, say, send a message twice, the hub asks first.

Compare runs

Two runs side by side — ideal for checking a repeat run against the original.

Fixed versions

Every save stores a new, unchangeable version of the workflow. Running executions keep their version — steps never change in the middle of a run.

Governance

When run details are pseudonymised, whether the evidence chain is intact and which anomalies were flagged.

Set the limits

Which module actions are allowed, how many runs per hour are permitted and how long history is kept.