Centum ERP · Golomax
Keep Centum ERP · Golomax in step with your orders, stock and finance, with the right person approving every posting.
3 ways to read, 1 way to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Centum ERP · Golomax, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Update Customers
customers.updateApproval by rule - List Customers
customers.listRead
Example flow
- Centum ERP · Golomax · List Customers
customers.listDone - Centum ERP · Golomax · Update Customers
customers.updateMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Centum ERP · Golomax.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Centum ERP · Golomax
- Centum ERP · Golomax's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
- Source actions
- 3
- Destination actions
- 1
- Data types
- 3
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
customers2
- List CustomersSource
List operation for Customers.
- Update CustomersDestinationNexra idempotency keyApproval before production
Update operation for Customers.
inventory1
- List InventorySource
List operation for Inventory.
products1
- List ProductsSource
List operation for Products.
Access and limits
- 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. 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.
Developer reference
- Create the Centum credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Centum ERP · Golomax, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/centum and the Connections API.