TriloAI

Integration

Keep SAP Business One orders, customers and inventory in sync without retyping

Connecting SAP Business One to n8n syncs orders, customers and inventory with your online store, CRM (customer relationship management system) and Google Sheets, so each record is entered only once. TriloAI usually connects through SAP Business One's official Service Layer, the interface SAP provides for other systems to read and write data, and any write to SAP can be set to wait for someone's approval. A single workflow usually launches in 1–2 weeks, and cross-system sync in 3–6 weeks.

Systems involved

  • SAP Business One (version for SAP HANA or Microsoft SQL Server)
  • SAP Business One Service Layer
  • n8n integration tool (cloud or self-hosted)
  • Online store or CRM (for example Shopify or HubSpot)
  • Google Sheets / LINE Official Account

Time to launch

A single workflow, such as syncing stock to a spreadsheet, usually takes 1–2 weeks; cross-system sync of orders, customers and inventory usually takes 3–6 weeks. Timing depends on the SAP version, the number of custom fields, how clean the data is and how many approval steps you want.

What runs automatically once connected

Store and website orders written to SAP

Starts when: A new order comes in from Shopify or your website

  1. 1Match it to SAP customer codes and item numbers
  2. 2Create a sales order by your rules, or place it on the approval list first
  3. 3Put orders with unmatched items, customers or prices on a pending list and alert sales
  4. 4Record the SAP document number back on the original order

Result: Orders no longer need to be typed into SAP, and you can see where each one came from and who approved it.

Customer records synced both ways

Starts when: A customer is added or edited in the CRM

  1. 1Check whether the customer already exists in SAP to avoid duplicates
  2. 2Create or update the business partner record (where SAP stores customers)
  3. 3Update the other side according to which system you decided is the source of truth

Result: Sales and accounting work from the same customer record instead of editing separate copies.

Inventory synced to your store and spreadsheets

Starts when: A scheduled check, for example every hour

  1. 1Read available stock for each warehouse from SAP
  2. 2Update your online store or the Google Sheets your sales team uses
  3. 3Alert purchasing about items below safety stock

Result: Stock figures on your website and in sales' hands follow SAP at the sync interval, with no manual matching.

Shipping notice to customers

Starts when: A delivery is created in SAP

  1. 1Read the shipped items, quantities and tracking number
  2. 2Email the customer, and send a LINE message to customers who have linked their LINE account
  3. 3Update the order status in the CRM

Result: Support no longer answers every has-it-shipped question by hand.

What to prepare

  • Your SAP Business One version, and whether Service Layer is installed and reachable from n8n
  • A dedicated SAP Business One user for the integration with only the permissions it needs; confirm licensing with your SAP partner
  • A field map for customer codes, item numbers, warehouses, price lists and payment terms
  • A decision on which system is the source of truth, such as SAP for customer master data and the CRM for contact history
  • Admin access to the online store or CRM
  • One contact who knows your order and shipping process; no engineer required

Good to know first

  • Service Layer must be installed and reachable. On Microsoft SQL Server, SAP Business One supports it from version 10.0; on older versions we fall back to a read-only database account or export files, which can do less.
  • SAP settings and user-defined fields differ by company, so the field map is checked field by field.
  • Documents written to SAP affect inventory and accounting, so we recommend requiring approval before anything is written.
  • If the SAP server is only on your internal network, n8n must be able to reach it, which usually means running n8n on a company server or setting up a secure connection.
  • LINE notices only go to customers who added your account and linked it, and messages you send count toward your LINE Official Account plan's monthly message allowance.

Frequently asked questions

Can SAP Business One be connected to n8n?
Yes. SAP Business One has an official Service Layer that lets other systems read and write data over a network connection. It is available on the SAP HANA version and, from version 10.0, on the Microsoft SQL Server version. n8n uses it to read and write orders, customers and inventory without changing SAP itself.
Can it read the custom fields we added?
Usually, yes. Service Layer supports SAP Business One user-defined fields, so fields your team added can be read and written too. We confirm the exact fields one by one when building the field map.
Could wrong data end up in SAP?
Writes to SAP can be set to wait for someone's approval. Records with unmatched items, customers or prices go to a pending list instead of being written. Every action is logged, so you can see who approved what and when.
Do we need our SAP partner's help?
Usually, yes. They can confirm the Service Layer installation, how it can be reached and the licensing for the integration user. We prepare the questions so you can simply forward them.
How long does it take to launch?
A single workflow, such as syncing stock to a spreadsheet, usually takes 1–2 weeks. Cross-system sync of orders, customers and inventory usually takes 3–6 weeks. Timing depends on the SAP version, the number of custom fields, how clean the data is and how many approval steps you want.

Check how your systems connect first

Bring the systems you use and how you work today. In a free 30-minute call we check whether they can connect and which part to start with. Pricing is scoped to your needs.

Book a free 30-minute consultation