What it is and what it is for
“Where is my order?” Operational sources mirror data from your systems: orders, shipments, prices, quotes, invoices and returns. The records are not embedded in the knowledge index. Important: the agent reveals customer data only after proof, and then only the records of that proof.
How it works
- Open Knowledge Base AI → Operational sources and click Add source.
- Name it and choose the Connection: Pull REST (HTTPS JSON), JSON file (HTTPS), JSON records, Push (ingest URL), Price list (manual) or a ready-made connection such as JTL-Wawi or Holded.
- On the Connection tab, enter the HTTPS address and the sign-in. For Push, copy the Ingest URL after saving.
- On the Mapping tab, map fields such as order, postal code, phone and tracking number.
- On the Proof tab, choose: order number and postal code, SMS one-time code, or caller number on the phone agent.
- On the Preview tab, run Preview without saving. Save and click Sync now.
Good to know
- Public HTTPS addresses only, no SQL editor.
- The SMS code goes to the number on the record, only if the caller agrees. Caller number proof works on the phone only.
- Status messages to customers (Messages tab) are off by default.
- Paid feature: fetches, new or changed records, messages and stored records. See Show usage.
- For GLS and DB Schenker there is a separate article on shipment tracking.