All connectors
Implemented
ERP & business operations
Centum ERP · Golomax logo

Centum ERP · Golomax

Reduce manual data entry between business systems.

Reduce manual data entry between business systems.

Source actions

3

Destination actions

1

Data types

3

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

customers
  • List Customers
    Source

    List operation for Customers.

  • Update Customers
    Destination
    Duplicate protected

    Update operation for Customers.

inventory
  • List Inventory
    Source

    List operation for Inventory.

products
  • List Products
    Source

    List operation for Products.

Authentication

signed access token

Before you build a flow

  • Customer reads use Centum signed access-token headers and numbered pagination. Dedicated API consumer access must be enabled by Centum or Golomax's administrator. Provider documentation URL currently returns 404; request contract is verified against Centum's published n8n integration. Existing customers can be matched by unique email and their names updated with read-back verification. Product and inventory reads are implemented. Product prices and per-warehouse inventory/source codes are not returned by these reads. Centum article IDs are not Magento SKUs: establish an explicit identifier mapping and choose the destination inventory source before sending stock. Customer creation, price writes, order creation and delivery status synchronisation require further vendor contracts and business configuration. Live instance validation remains pending.