Glossary
Who this is for: anyone who meets a word in Liitora or this guide and wants to know what it means.
Before you start: nothing.
The terms are in alphabetical order. Each one links to the page that explains it in full.
| Term | What it means |
|---|---|
| Action | A reusable building block that a step uses, such as “send an email”; see built-in actions and action references. |
| Activation | Turning a version on, so its schedules and triggers start it and it runs in production; see Approve a workflow. |
| Activation policy | A per-workflow rule: either a person approves each version (the default), or the AI assistant may activate versions whose tests pass. |
| Active | The status of a workflow that runs on its triggers. |
| Admin | The role that can do everything, including approving workflows and showing secret values; see Manage users and roles. |
| Alert rule | A rule that says which events (such as a failed run) are sent to which channel; see Set up alerts. |
| AI assistant (agent) | Your own Claude, Copilot or other assistant, working in Liitora through MCP; it builds and tests but never approves or sees secret values. |
| API token | A key, starting with liitora_, that lets a script or assistant call Liitora with the permissions it was given (never more than its creator holds) until it expires, at most a year; see Create API tokens. |
| Approval | A person’s decision that one exact version may run; the author of a version can never approve it. |
| Archived | The status of a workflow that is stopped for good and can’t be changed; its history stays. |
| Artifact | A file a step makes, such as a CSV report; later steps can use it and you can download it from the run. |
| Audit log | The record of every change and who made it, which nobody can edit; see Page: Settings. |
| Badge | The status of an action version: Draft, Tested, Proven or Deprecated; see Page: Library. |
| Blackout | A period your company sets when scheduled runs should not happen, used with the tenant_blackouts calendar. |
| Built-in action | An action that is part of Liitora, written platform/<name>@v1; see built-in actions. |
| Calendar | A list of days, such as Finnish public holidays, that a schedule can skip or move away from; see Use calendars and holidays. |
| Channel | Where alerts go: email, Microsoft Teams, Slack or a webhook of yours. |
| Company (tenant) | Your organisation in Liitora; everything you do is kept apart from other companies. |
| Company variable | A plain value that every workflow of your company reads as vars.<name>, such as a report recipient; see Use company variables. |
| Compute unit (CU) | The measure of how much work a run used, from its run time, CPU and memory; see What is a compute unit. |
| Connection | How Liitora reaches one of your systems: its address, sign-in method and the names of the secrets it uses; see Create a connection. |
| Digest | A summary email: the weekly health digest, or a daily digest of alerts. |
| Draft | The status of a workflow that is saved but has never been activated. |
| Dry run | A test run that reads from your systems for real but skips writes. |
| Editor | The role that builds and runs workflows and manages connections, webhooks and secrets, but can’t approve or show secret values. |
| Environment | Test or Production: each connection can have a setup for each, and test runs use the test setup. |
| Fill link | A link that opens a small page where a person adds a secret value; see Add a secret. |
| For-each | Running one step once per item of a list; see the workflow format. |
| Freshness expectation | A promise that a workflow succeeds by a time, for example 09:00 every weekday, with an alert if it doesn’t; see Set freshness expectations. |
| Idempotency key | A stable id sent with a request so that the receiver can ignore a repeat of it; Liitora sends one per step and uses one for webhook deliveries. |
| Incident | A group of related alerts, such as repeated failures of one step, that stays open until it is resolved. |
| Library | The list of actions: built-in, the platform library and your own; see Page: Library. |
| Lookup table | A small company table, such as cost centre codes and names, that workflows read with lookup(); every save is a new version; see Use lookup tables. |
| MCP | The Model Context Protocol, the standard way AI assistants use tools; see MCP tools. |
| Operator session | A time-limited, reasoned and audited visit by our staff to your company; see What “managed by us” means. |
| Paused | The status of a workflow that doesn’t start new runs, because a person, a billing problem or a plan limit paused it. |
| Permission | One thing a person may do, such as Reveal secrets; roles are sets of permissions; see Manage users and roles. |
| Platform library | Actions we curate for all customers, written library/<name>@vN. |
| Required minimum | The kinds of test cases a workflow must have before it can be activated, such as a test for a failing upstream system; see Read and write workflow tests. |
| Role | A set of permissions: Admin, Editor, Viewer or AI assistant. |
| Run | One time a workflow ran, with its status, steps, logs and files; see Page: Run. |
| Secret | A password, API key, token or certificate that only people can enter or see; see Add a secret. |
| Secret request | A secret your AI assistant asked for by name, waiting for a person to add the value. |
| Signing secret | The key a webhook sender uses to sign its requests, so Liitora knows they are genuine; see Webhook signing. |
| Step | One thing a workflow does, such as “fetch the orders”. |
| Template | Stored HTML with places for values, used by email.send and pdf.render; see Use email and PDF templates. |
| Test case | A description of one situation (fake input and answers) and what the workflow must do in it; see Test case format. |
| Test run | A run of any version, draft included, with your test connections. |
| Trigger | What starts a run: a schedule, a webhook, another workflow, a person or the API; see the workflow format. |
| Version | A saved, unchangeable copy of a workflow; each save makes a new version. |
| Viewer | The read-only role. |
| Webhook endpoint | A Liitora address that another system sends events to, which starts workflows; see Set up a webhook. |
| Workflow | One automation: when it runs and the steps it takes. |
| Workflow library | Ready-made workflows that Liitora wrote, tested and signed, which your company takes into use with a second person’s approval; see Take a library workflow into use. |