Connector library

Implemented source Commerce, Finance & Operations APIs

Fluent Commerce connector.

Read visible Fluent Commerce location reference pages and exact location ID/ref/name/type/status metadata through two named account-scoped GraphQL actions.

Connector download

Download Fluent Commerce

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
Account Code, Environment
Package size
9 KB
SHA-256
4e40d019c67db9b1a7212c449b6bb84053856565d8cf661ef396428fa6f7c33e

Version history

What's new

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

    Two named account-scoped GraphQL reads return one native location page and exact selected location metadata, with managed Bearer credentials and checked last-edge continuation. Replaces the generic scaffold; hosted and live validation remain pending.

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

    Historical configurable HTTP scaffold; not a vendor-specific implementation.

Included in this version

Included actions

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

List location references

Read one checked native cursor page of visible selected location metadata.

Get location

Read selected location metadata by exact ID within the account/token scope.

Vendor API

API and access

Implementation considerations
  • Location reference pages: Read one native cursor page of visible location IDs, refs, names, types and statuses.
  • Exact location lookup: Read selected location metadata by its exact ID within the account and token scope.
  • Scoped no match: Keep a native nullable lookup distinct from API failure or global absence.
  • Caller-managed reads; no inventory, orders, workflow actions or writes are included.
  • Account Code is the approved single DNS label for the documented account API host. Sandbox uses https://{account}.sandbox.api.fluentretail.com/graphql; production uses https://{account}.api.fluentretail.com/graphql. The issued OAuth access token belongs in a managed Bearer Token credential and uses Authorization: Bearer. Token issuance, refresh and LOCATION_VIEW permission remain external; shared regional endpoints require a separate routing contract.
  • Page Size uses native first with a local 1–100 cap, default 100. After Cursor is blank initially, then the exact returned nextCursor. PageInfo has no endCursor: continuation uses the last native edge cursor. Missing, repeated, excessive or non-advancing pages fail; no automatic enumeration, total, snapshot or complete-account coverage is claimed.
  • Selected ref/name/type/status fields retain null and empty strings; missing fields fail. IDs preserve exact case and zeroes within the declared ASCII subset. Native locationById: null means no match only within account/token scope. Partial GraphQL errors and HTTP 404 remain failures. Status and type are metadata, not inventory, opening hours or routing readiness.
  • Request Budget is 1000–8000 ms shared by transport and validation, default 7000; strict UTF-8 JSON has a 1 MiB response cap. Normal TLS verification remains enabled, redirects and environment proxies are disabled, and failures are not replayed. Hosted import, saved mappings, executor dependencies and live account/environment/token/role/query checks remain untested.
  • Two packaged account-scoped GraphQL reads return one native location page and exact selected location metadata. Public schema, environment, authentication and permission guides establish the contract; live account/token/RBAC/query behavior and hosted dependencies need validation.

Support

Need help with Fluent Commerce?

Tell us what you need to connect or change.