Use casesHow it worksSecurityPricingDocs Request early access
Connect your business systems, safely

Ask your AI to connect your systems. You approve it. Liitora runs it.

Tell Claude, ChatGPT or Copilot what should move between your web shop, accounting or ERP. It asks the right questions first, and nothing runs until you approve it. The AI never gets your passwords.

Need a yes from whoever looks after your IT? Send them this page

How it works

From a chat to a running integration, in five steps.

Liitora is an integration platform with no AI of its own. You keep the AI assistant you know, Claude, ChatGPT or GitHub Copilot, and connect Liitora to it. The assistant does the talking; Liitora keeps the plan, the drafts, the keys, the approvals and the runs.

Your AI assistant Claude, ChatGPT or Copilot You Send new shop orders to our fulfilment partner. Your AI, before it builds If the partner rejects an order, who should hear? You The shop team. Your AI Here is the plan. Shall I build it? What the AI can't do ✕ Approve anything ✕ See a password or key ✕ Run or reach your systems Liitora Keeps the plan, the keys, the approvals and the runs Connector 1 drafts ✕ can't approve 2 Plan saved Kept with the workflow 3 Draft and its tests Tests must pass first 4 Approval Plan and version together Keys and passwords People add them through a link. The AI sees only names. You or a colleague read and approve, in Liitora 5 Runs exactly the approved version The same way every time, in a sandbox, no AI Retries, alerts, every run logged step by step Audit log Who wrote it, who approved it, what it can reach and every run Your systems Only the ones it declares Web shopWooCommerce orders AccountingInvoices and payments ERPPrices and stock Partner APIOrders to pack and ship Anything elseRefused ✕ Your AI assistant Claude, ChatGPT or Copilot You Send new shop orders to our partner. Your AI, before it builds Who should hear if the partner rejects an order? 1 Connector: plans, drafts ✕ can't approve Liitora The plan, the keys, the approvals, the runs 2 Plan savedKept with the workflow 3 Draft and its testsTests must pass first 4 You or a colleague approveThe plan and the version, in Liitora Keys and passwordsAdded by people. The AI sees only names. 5 Runs the approved version Same way every time, no AI, all logged Audit logWho wrote it, who approved it, every run Your systems, only the declared ones Web shopWooCommerce orders AccountingInvoices and payments ERPPrices and stock Partner APIOrders to pack and ship ✕ Anything it doesn't declareRefused
The AI only works on plans and drafts. Approval, keys and your systems stay on Liitora's side, with people.
  1. Once, in your AI assistant

    Connect Liitora to your assistant

    Add Liitora as a connector in Claude or ChatGPT and sign in with your Liitora account, or give Claude Code or VS Code an API token. No browser extension, and no password goes into the chat. Your assistant can now use Liitora's tools as you, in your company only.

    Connect your AI assistant
    Connectors in your AI assistant
    • ✓Read workflows, runs and connectionsAllowed
    • ✓Save plans and drafts, run their testsAllowed
    • ✕Approve, or see a password or keyNever
  2. In your AI assistant

    Answer its questions, confirm the plan

    Ask in your own words. It asks the questions an integration architect would, at your level, and shows you a plan. Liitora won't let it build until that plan is saved, and keeps the plan with the workflow, so the next change starts from it.

    You In your AI assistant

    Every 5 minutes, send new WooCommerce orders to our fulfilment partner's API. Never send the same order twice.

    AI The plan, before it builds

    Every 5 minutes, read new paid orders and send each one once. If the partner rejects an order, set it aside and email the shop team. Shall I build it?

  3. Saved in Liitora

    It builds a draft and tests it

    When you confirm the plan, it writes the workflow and its tests, and runs them against example answers. A draft can't run in production. When a step needs a password or key, it sends you a link to a Liitora page where you add it. It never sees the value.

    Shop orders to fulfilment Draft
    • Plan saved version 1
    • Workflow tests 5 of 5 passed
    • Partner API key waiting for you to add it
  4. In Liitora, not in the chat

    You or a colleague approve it

    Its tests must pass first. Then a person reads the plan beside the version: what it does in plain English, what changed, and every system it would reach. The AI can't approve. In a small company the person who asked may approve. To always need a second person, an admin turns that on, and on Business it is on from the start.

    Who may approve
    The plan

    Plan version 1, written with this version

    What changed in what it can use
    • @Email to the shop team new in this versionAdded
    Approver: Anna, operationsApprove
  5. In Liitora, every time

    Liitora runs exactly that

    On a schedule or a webhook, with retries and alerts. The AI that wrote it plays no part here. Liitora's own code runs the approved version the same way every time, and every run is logged step by step.

    • Read the waiting orders340 ms
    • Find the orders not sent yet 3 new6 ms
    • Send 3 orders one retried1.2 s

Want a head start? See ready-made workflows in the library.

What it connects

Connect WooCommerce, Odoo, your ERP or any system with an API.

Most integrations are the same job: read what is new or changed in one system, put it in the shape the other system wants, and send it on.

From WooCommerce New orders in your WordPress shop
Liitora, every 5 minutes
  1. Reads new orders from the shop's API
  2. Keeps only the ones not sent yet
  3. Maps the fields to the partner's format
  4. Sends each order, and retries if the partner is busy
To Your fulfilment partner Orders to pack and ship, through their API
An example you can build: web shop orders go to the partner who ships them, without anyone copying them.

More of what people connect

  • Odoo to Your accounting

    Confirmed sales orders become invoices in the accounting system, and paid invoices are marked paid back in Odoo.

  • Your ERP to Your web shop

    Prices and stock levels go to the shop. Only the products that changed are sent.

  • Your CRM to Odoo

    New and changed customers are created or updated in Odoo, matched by their customer number.

  • Partner SFTP to Your ERP

    Order files in CSV or XML are picked up, checked and posted to the ERP's API, with a receipt for each file.

  • HR system to Microsoft Entra ID

    New starters get their accounts and groups, and leavers lose their access.

  • Any system with an API to Any other

    No connector to wait for. Your AI assistant reads the system's API docs and writes the integration.

What every sync needs, already there

  • Sends only what changedLiitora compares with the last run, or with what the other system has, so only new, changed and removed records go on.Find what changed
  • Nothing is lost when a run failsWhat a sync remembers is saved only when the whole run succeeds, so the next run sends the same changes again.What a sync remembers
  • Retries and request limitsTries again after timeouts and "too many requests", and keeps to a request limit you set for each system.Set a request limit
  • One bad record doesn't stop the restAn order that keeps failing is set aside, the others still go, and you replay it after you fix it.Replay set-aside items
Is it safe?

Why an AI can't run loose in Liitora.

When AI agents cause damage, it is usually the same story: the agent held live keys, decided what to do while it ran, and nobody approved the step. Liitora takes away all three.

  • The AI never holds the keys

    It writes drafts and tests. People add the passwords and keys, and the AI only ever sees their names.

    • It can't approve a version
    • It can't read a secret value
  • What runs is fixed

    A person approves one exact version. That version runs as written, the same way every time, in a sandbox.

    • It reaches only the systems it declares
    • Nothing improvises while it runs
  • You can prove it

    Who wrote it, who approved it, what it can reach and what it did, in an audit log that can't be edited.

    • Every run logged, secrets masked
    • Export everything at any time

Approval protects you only if you can read what you approve. So every approval shows what the workflow does in plain English, what changed, and every new system or address it would reach.

Using an AI step inside a workflow, for example to sort emails? Its answer only fills in values and can't add or change a step. The approver sees every place an AI answer could be sent, and an admin can turn AI steps off. AI in workflows

Why Liitora

Why not a consultant, an AI agent or an automation tool?

Until two systems are connected, someone copies orders, invoices or customers by hand. Most of what an integration costs isn't the software: it's working out what should happen, building it safely and keeping it running.

  • A consultant project

    Workshops and a specification, consultant days to build and test it, and a change request for every later change.

    With Liitora Your AI assistant asks an integration architect's questions, at your level, and shows you a plan. A change is a conversation and a new approval, not a new project.

  • An AI agent with your keys

    It decides what to do as it runs, with live keys, and nobody approves the step. Whoever looks after your IT will say no, and they are right.

    With Liitora The AI only designs. What runs is the version you approved, the same way every time, and the AI never sees your passwords.

  • A general automation tool

    Quick to start, and many now have AI too. An integration that must not lose or double an order needs more: a plan someone checked, a sign-off, and a record of who approved what.

    With Liitora The plan is required and kept with the workflow, a person approves the plan and the version together, and sending only what changed, retries and setting bad records aside are built in.

For a large project you may still want a consultant. With Liitora, they spend their time on the hard decisions, not on writing and testing the integration. How the assistant asks before it builds

Who builds Liitora

Made by people who have done this before.

Liitora is founded by Matti Lehmus, co-founder of Feedtrail and its Head of Integrations from 2015 to 2022. With major US health systems, his team took on one of HL7's biggest gaps, its missing security, and built an end-to-end encrypted integration layer with fully isolated customer environments. Feedtrail was named Best in KLAS 2024 and acquired by Relias in 2025.

Hosted in HelsinkiOn UpCloud, in Finland. Your data stays in the EU.Where your data goes
A Finnish companyLiitora is run by a Finnish company, registered in the Finnish Trade Register. You know who you deal with.hello@liitora.com
DPA and subprocessorsPublished before launch.
Not ISO 27001 certified yetWe say so, and describe every control instead.What we do instead
Pricing

One flat price a month. No surprise bills.

Every plan has unlimited people and workflows, and every safety control. You pay for the plan, not for each person or each run.

We publish prices soon. Early-access customers get half price for their first year.

Starter

For a small team that wants its first integrations done safely.

Price coming soon

A flat monthly price, excl. VAT

  • Approval, tests, audit trail and export
  • Schedules every 15 minutes
  • Run logs kept 30 days
  • Email support within 2 business days

Business

For a medium-sized business where someone else checks every change.

Price coming soon

A flat monthly price, excl. VAT

  • Everything in Team
  • A second approver for every change, on by default
  • Run logs kept 90 days
  • Schedules every minute
  • Support the next business day
Planned for larger companies
  • Single sign-on (SSO) and SCIM Coming soon
  • Audit and logs to your SIEM Coming soon
  • Your own encryption keys (BYOK and HYOK) Coming soon
  • Runner groups in your own network Coming soon
Try Business for 14 daysNo card needed. When the trial ends, nothing is charged: workflows pause, and you can export everything for 30 days.
Need more runs one month?Add a run pack for that month instead of changing your plan. Nothing is billed unless you choose it.
Small company?Companies under 20 employees get Business at half price. Early-access customers get half price for their first year.
Our pricing promise
  • Building and testing are always free: test runs and dry runs never count.
  • 90 days' notice before any price or limit change, and no silent cuts.
  • A public definition of a run: one start of a workflow, however many steps it has.
Questions

What people ask first

How does my AI assistant connect to Liitora?

You add Liitora to your assistant as a connector. It uses MCP (the Model Context Protocol), an open standard that Claude, ChatGPT, GitHub Copilot and other assistants support. In Claude or ChatGPT you add a custom connector and sign in with your Liitora account. In Claude Code or VS Code, you use an API token that an admin creates. There is no browser extension, and no password or key goes into the chat.

The assistant then uses Liitora's tools: it reads your workflows and runs, saves its plan and its drafts in Liitora, and runs their tests. It can't approve anything.

How do I know the AI asked the right questions?

Liitora's tools tell the assistant what an integration architect asks, and the assistant shows you its plan before it builds. Liitora refuses to save a new or changed workflow from the assistant until it has saved a plan for it, so it can't skip that step.

The plan is stored with the workflow. Whoever approves reads it beside the exact version that would run, so a missing answer shows up there, not in production. The next change starts from the same plan.

Do I still need an integration consultant?

Often not. Your AI assistant asks what a consultant would ask in a workshop: what should happen, which system is the source of truth, what to do with duplicates and errors, and who approves. It explains in plain words if you are new to this, and keeps it short if you are technical. Then it shows you a plan, and it builds nothing until you confirm it.

For a large project you may still want a consultant. Then they spend their time on the hard decisions, not on writing and testing the integration.

Is Liitora an AI agent?

No. Your AI assistant designs workflows through Liitora, but what runs is the version a person approved, exactly as written. Liitora has no AI of its own.

A workflow uses AI while it runs only if you add an AI step. The approver sees and confirms it, and an admin can turn AI steps off for the whole company.

What if the AI writes something harmful?

It saves a draft, and a draft can't run in production. Its tests must pass. Then a person reads what it does, what changed and every system it would reach before it can run. An AI assistant can't approve.

Can the AI change a workflow after it's approved?

It can save a new draft. The approved version keeps running unchanged until a person approves the new one.

How is Liitora different from other automation tools with AI?

Many automation tools now let AI help build a workflow. Liitora is built around what happens next: the assistant must write a plan before it builds, tests must pass, a person approves the plan and the exact version together, the AI never sees a password or key, and every change and run is on record. It runs in Helsinki, Finland.

A free, self-hosted tool can be enough if your team runs the servers, applies the security patches, and builds the approvals and the audit trail around it. If you only need a quick personal automation, a general tool may suit you better.

What counts as a run?

One production start of a workflow, from its trigger to its end, however many steps it has. Test runs, dry runs and workflow tests never count.

Where is my data?

Liitora runs on UpCloud in Helsinki, Finland, and run logs and files stay there. Each workflow shows where its data goes before you approve it.

Can I leave and take my workflows with me?

Yes. Workflows are plain YAML files you can read, and you can export everything your company has in Liitora at any time.

When will prices be published?

Soon, once our production costs are confirmed. Every plan is a flat monthly price, excluding VAT. Ask us for early access and we tell you the price before you commit to anything.

Tell us the two systems you need to connect.

We set it up with you in the pilot, on your systems, with your approvers. If Liitora isn't the right tool for it, we tell you.

Or write to hello@liitora.com

Suomeksi

Liitora on suomalainen integraatioalusta pienille ja keskisuurille yrityksille. Liität sen tekoälyavustajaasi, ja avustajasi kysyy ensin samat kysymykset kuin integraatioarkkitehti ja näyttää suunnitelman ennen kuin rakentaa mitään, usein ilman erillistä konsulttiprojektia. Se suunnittelee integraation kahden järjestelmän välille, esimerkiksi WooCommerce-verkkokaupan tilaukset logistiikkakumppanille tai Odoon myyntitilaukset kirjanpitoon. Sinä tai kollegasi hyväksytte sen Liitorassa, ja Liitora ajaa täsmälleen hyväksytyn version. Tekoäly ei näe salasanoja eikä voi hyväksyä omaa työtään.

Palvelu toimii Helsingissä, ja tietosi pysyvät EU:ssa. Sivusto ja ohjeet ovat englanniksi, mutta voit kirjoittaa meille suomeksi: hello@liitora.com.