Connector library

Implemented source Enterprise, ERP & HR APIs

SAP Business One connector.

Read bounded business partner and item reference pages and selected exact metadata through four SAP Business One Service Layer OData v4 actions using an issued managed session token.

Connector download

Download SAP Business One

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Connection settings
Route ID, Service Origin
Package size
10 KB
SHA-256
1ec54dd33053ad01efb8375ddbb02d101425401aecd912465d7110c0db449635

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Four explicit Service Layer OData v4 GET reads replace the generic HTTP scaffold: bounded business partner/item reference pages and selected exact code metadata using a managed native session cookie.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical configurable HTTP scaffold without implemented vendor actions.

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List business partners

Read one bounded returned business partner reference page.

Get business partner

Read selected name/type metadata for an exact CardCode.

List items

Read one bounded returned item reference page.

Get item

Read selected name/foreign-name metadata for an exact ItemCode.

Vendor API

API and access

Implementation considerations
  • Business partner references: Read one bounded returned code/name/type page or selected metadata for an exact CardCode.
  • Item references: Read one bounded returned code/name/foreign-name page or selected metadata for an exact ItemCode.
  • Caller-managed reference reads; no synchronization job or webhook trigger is included.
  • Set the operator-approved Service Layer HTTPS origin. The connector appends /b1s/v2 and fixed entity paths; standard certificate/hostname verification is required.
  • Store the raw issued B1SESSION in a managed bearer-token credential. The connector sends its native session cookie without an Authorization header. Route ID is an optional issued .nodeN routing hint; supply it when required by the target topology. Login/company selection, logout and refresh remain external.
  • Exact string keys preserve leading zeroes and case. Supported local subsets are 15-character business partner codes and 20-character item codes; validate code coverage before migration. Selected nullable/empty names and future type text are preserved, without stock, financial, transaction or readiness claims.
  • Page Limit/Row Offset map to bounded top/skip. Continuation presence is recorded only as metadata; links are not followed or echoed and absence does not prove complete coverage. Caller owns iteration budgets, consistency and completeness checks.
  • No writes, financial/employee transactions, stock/price quantities, orders/invoices, DI API, OData v3 or arbitrary entity/filter input is included. Hosted import, executor dependencies/URL support and live company/session/role/certificate/field/paging behavior need validation.
  • The package implements four Service Layer OData v4 reference reads with an externally issued session. Public examples are not a live company schema; validate session, routing, access and supported code coverage in the target environment.

Support

Need help with SAP Business One?

Tell us what you need to connect or change.