Connector library

Implemented source Commerce, Finance & Operations APIs

ShipBob connector.

Retrieve ShipBob product and variant summaries, inspect inventory metadata and aggregate stock quantities, and list fulfillment-center summaries.

Connector download

Download ShipBob

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.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
9 KB
SHA-256
003bf323e56cc7219c8f1dd2c203753abe03fbf44d408717644e756fb3a2f9d3

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Retrieve product/variant summaries, inventory metadata, aggregate stock quantities and fulfillment-center summaries through four named read actions against the 2026-07 API.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Retrieve ShipBob product and variant summaries, inspect inventory metadata and aggregate stock quantities, and list fulfillment-center summaries.

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

    Retained immutable historical scaffold archive.

Included in this version

Included actions

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

Get product

Retrieve selected product and variant summaries with exact string IDs and explicit variant cap.

Get inventory

Retrieve selected inventory identity, SKU and variant flags.

Get inventory levels

Retrieve distinct aggregate vendor inventory quantities without computing availability.

List fulfillment centers

Retrieve up to 100 selected center summaries with explicit truncation evidence.

Vendor API

API and access

Implementation considerations
  • Confirm whether the customer needs order reads, order creation, inventory, refunds, fulfillment, or marketplace-specific behavior.
  • Use external IDs, order IDs, fulfillment IDs, and payment IDs to avoid duplicate work during retries.
  • For broad commerce APIs, start with get/search/create/update order, customer, product, and fulfillment actions.

Support

Need help with ShipBob?

Tell us what you need to connect or change.