Any system that can send a webhook — shop platform, form builder, monitoring, alarm — can trigger a chore on the box. Your Aivell receives the call, reads the payload, and acts with full context across email, spreadsheets and your database. The integration your two systems never shipped, written in plain language.
starts when: One of your systems sends a webhook to the box
Every office has two systems that refuse to talk to each other. The shop doesn’t tell the warehouse sheet; the form tool doesn’t tell the database; the alarm tells nobody until Monday. The vendor’s answer is an integration that’s “on the roadmap”; the practical answer is a person who copies data from one screen into another, several times a day — exactly the kind of work that swallows 62% of employee time.
Hosted glue services exist, but they route your business data through a third party and top out at “when X happens, do Y”. Real procedures have lookups, exceptions and judgment in the middle.
One box, one plain-language chore, and the integration your vendors never shipped has been running since Tuesday — with every webhook it ever received sitting in the audit trail.
No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:
when the shop marks an order paid, the webhook fires this chore
look the customer up in the database; first order gets a welcome line
append the order to the fulfilment sheet for the warehouse
orders over €500 wait for a yes from Davide before confirming
address looks incomplete? email the customer and ask, in their language
shipping outside the EU adds the customs note and a flag for Davide
email the customer a confirmation with the expected ship date
log every webhook received; payloads that fit no rule go to a review list
Connected with single-click passkeys — no copied tokens, no OAuth hell.
Every tool can be limited to exactly what this chore needs. For this one, you might set:
Practically all of them. Webhooks — "call this address when something happens" — are the one integration feature almost every shop platform, form builder, booking system and monitoring tool ships. If a system can send one, it can start a chore on the box.
No. The sending system calls your box directly — the payload crosses your firewall once, inbound, and everything after that happens on your premises. There is no relay service in the middle reading your order data.
Nothing irreversible. A payload that matches no rule in the chore is parked on a review list and shows up in the log — the chore acts on what it understands and asks about the rest. Senders you never registered don't even get that far.
Two ways. The logic runs on your box, so the data in the payload stays yours. And the "recipe" is a plain-language chore with judgment in it — look things up, weigh exceptions, ask a human over €500 — not a brittle chain of if-this-then-that blocks.
A webhook fires in one system, your Aivell writes the record correctly into the other — on-premise glue between your tools, with guardrails on every insert.
An on-premise AI colleague watches your database and speaks up only when a threshold breaks — with the numbers, the trend and the context attached.
Purchase orders arriving by email — PDF, scan, photo or plain text — read onboard, checked against your prices, entered into your system, confirmed back.
Order status, returns and price checks handled by a private AI colleague — onboard inference, so customer data never leaves your shop.
An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.
You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.
onboard inference · air-gapped · fixed monthly fee