When one system fires a webhook — a new order, a signed contract, an updated customer — an Aivell catches it, looks up the matching record, and writes the data correctly into the other system's database or sheet. Exceptions are flagged to a human, and existing records are never overwritten.
starts when: Your shop fires a webhook — a new order just landed
Two systems, no bridge, one human in a swivel chair. The order exists in the shop; someone retypes it into the ERP. The contract is signed in one tool; someone updates the customer file in another. It’s the same record, keyed twice, with all the drift that implies — a mistyped account code here, a skipped order there, discovered weeks later when the numbers won’t reconcile.
The integrations exist, in theory. In practice they mean a cloud connector with your customer data flowing through a third party, or a custom script nobody dares touch since the developer left. So the retyping stays.
The guardrail worth underlining: the database tool can insert but can never update or delete. The sync physically cannot trample a record that already exists — a property no flowchart connector gives you, enforced on the tool itself.
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 sends a new-order webhook, read the payload
look the customer up in the ERP by email address, then by VAT number
known customer — insert the order under their existing account code
new customer — create the record, but flag it for Jonas to verify
currency other than euro? convert at the booked rate, keep the original amount in the notes
append a line to the operations sheet so the day's list stays complete
if the ERP insert fails, retry once, then email Jonas with the full payload
never update or delete existing orders — inserts only
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:
They connect the same boxes, yes — through their cloud, with your data in transit through their servers, and rules built in a flowchart editor. Here the glue runs behind your firewall, writes to your database directly, and the rules are sentences you can read aloud.
One retry, then a human. Jonas gets the full payload and the error, nothing is silently dropped, and the audit trail shows every attempt. The order is never half-booked.
No. The webhook arrives at the box, the lookup and the insert happen over your own network, and the reasoning runs onboard. The path from shop to ERP never leaves the building.
Yes — as a second chore in the opposite direction, with its own trigger and its own guardrails. Keeping them separate keeps each side's rules simple and auditable.
Any system that can send a webhook can trigger a chore — your shop, your form tool, your monitoring. The glue logic runs on a box in your office.
Purchase orders arriving by email — PDF, scan, photo or plain text — read onboard, checked against your prices, entered into your system, confirmed back.
An Aivell dedupes and normalizes customer records on a schedule, logs every proposed change, and touches nothing until a human approves. All onboard.
Order status, returns and price checks handled by a private AI colleague — onboard inference, so customer data never leaves your shop.
Shipment status answered, PODs read and filed, carrier portals worked overnight — an AI colleague that keeps your rates behind your firewall.
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