What Liitora does
Who this is for: anyone new to Liitora.
Before you start: nothing.
Liitora runs automations for your company. We call each automation a workflow.
For example, a workflow can fetch last week’s open orders from your order system and email a CSV of them to your sales team every Monday.
The words we use
Section titled “The words we use”- Workflow: one automation. It says when it runs and what it does.
- Step: one thing a workflow does, such as “fetch the orders” or “send the email”. Steps run one after another, or side by side when they don’t depend on each other.
- Action: a ready-made building block that a step uses, for example “send an email” or “call a web address”.
- Artifact: a file that a step makes, such as a report. Later steps can use it, and you can download it in the app.
- Connection: how Liitora reaches one of your systems: its address and how to sign in.
- Secret: a password, API key or token. Only people in your company can enter or see it.
If you know GitHub Actions, workflows work in a similar way. The glossary explains every other term.
Who does what
Section titled “Who does what”| Who | What they do |
|---|---|
| Your AI assistant | Writes workflows and their tests, runs tests and test runs, reads logs and explains failures. It asks you for passwords and keys, but never sees them. |
| People in your company | Add passwords and keys, review what the assistant made, approve it and turn it on. |
| Liitora | Checks every workflow before it is saved, runs it at the right time in a closed sandbox and keeps a log of every run. |
How it works
Section titled “How it works”- You ask your AI assistant. Tell Claude, Copilot or another assistant what you want in your own words. It writes the workflow for you through Liitora.
- You add the passwords and keys yourself. If a step needs to sign in somewhere, the assistant gives you a link to enter the key. The assistant never sees it.
- Liitora tests it. Every workflow comes with test cases. They run each time the workflow is saved, against fake answers, so nothing real is touched.
- A person approves it. You see what the workflow does in plain English, what changed and what the tests prove. Nothing runs for real until a person approves it. The assistant never approves its own work. A version a person wrote needs a second person, unless that person is the only approver.
- Liitora runs the workflow. You see every run, step by step.
When a workflow runs
Section titled “When a workflow runs”A workflow starts in one of these ways. You choose them in its on: section.
- On a schedule, for example every weekday at 08:00 Helsinki time. It can skip public holidays.
- When a webhook arrives: another system, such as GitHub or your own app, sends an event to a Liitora address.
- After another workflow finishes.
- By hand, when a person selects Run now, or when a program calls the API.
What Liitora does not do
Section titled “What Liitora does not do”- It doesn’t include its own AI. You use the assistant you already have.
- It doesn’t let a workflow reach your internal network or read files on our servers. Workflows run in a closed sandbox and can only call public HTTPS addresses.