Skip to main content

Overview

Once Centra is connected, the Dema Agent can pull live data from your store — products, variants, orders, customers, inventory, markets, pricelists, categories, and discounts — directly inside a conversation. With write permissions, it can also take action for you: correct stock, confirm or cancel orders, create shipments, update products and customers, and turn discounts on or off. The agent only acts when you ask it to, and Dema asks you to confirm sensitive changes before they are applied. You stay in control of both what the agent can see and what it can do.
This is a separate connection from the Centra data integration that syncs orders and inventory into Dema’s analytics. That one is a read-only background sync; this one lets the agent read and act in real time when you ask. They use different credentials — see below.

Use a dedicated token for the agent

Create a new Integration API token just for the agent, separate from the one your data sync uses. The agent can act on your store, not just read it, so its own token keeps access independently scoped, auditable, and revocable — cutting the agent off or rotating its token never touches your analytics sync. Name it something obvious like Dema Agent.

Prerequisites

  • A Centra account with permission to create Integration API tokens (System → API Tokens).
  • Your store URL, in the form https://your-store.centra.com.

Connect Centra

1

Create a dedicated API token in Centra

  1. In Centra, go to System → API Tokens.
  2. Click Create integration API token in the top right.
  3. Give it a description and set Integration name to Dema Agent (create it if it does not exist).
  4. Set an expiry date. Centra tokens are time-limited (30 days by default); pick a window that fits your rotation policy.
  5. Leave Restrictions unchecked, or scope them if your security team requires it.
  6. Under Permissions, select the permissions listed in Permissions to grant below. Grant the read set for analysis; add write permissions only if you want the agent to make changes.
  7. Click Save and copy the generated token.
2

Connect in Dema

In Dema, go to Agents → Settings → Integrations, find Centra, and click Connect. Enter:
  • API token — the token you just created.
  • Account URL — your store URL, for example https://your-store.centra.com.
Click Add. Dema verifies the credentials and marks the integration as Active.

Permissions to grant

Centra permissions are granular and chosen when you create the token. We recommend the principle of least privilege: grant the read set so the agent can analyze your store, and add write permissions only for the actions you actually want it to perform.
Centra tells you the exact permission every request uses. If the agent ever reports a missing permission, Centra’s error names the precise one — add it to the token and reconnect. This is also the surest way to grant the agent the minimum it needs and nothing more.
Grant these so the agent can answer questions across your catalogue, orders, customers, inventory, and pricing.
PermissionWhat it unlocks
Product:readRead products and their details
ProductVariant:readRead variants (colours, styles)
ProductSize:readRead sizes, SKUs, and EANs
Brand:readRead the brand on a product
Collection:readRead the collection a product belongs to
Display:readRead catalogue items shown to shoppers
Bundle:readIdentify bundle products
PermissionWhat it unlocks
Warehouse:readRead warehouses and stock locations
ProductVariant.stock:readRead stock levels per variant
ProductSize.stock:readRead stock levels per size
PermissionWhat it unlocks
Order:readRead orders, line items, and totals
Order.shippingAddress:readRead shipping addresses on orders
Order.billingAddress:readRead billing addresses on orders
Return:readRead return details on an order
PermissionWhat it unlocks
Customer:readLook up customers and their order history
Customer.billingAddress:readRead a customer’s billing address
PermissionWhat it unlocks
Market:readRead markets and sales channels
Store:readRead stores
Pricelist:readRead pricelists
Category:readRead the merchandising category tree
Voucher:readRead discount codes and vouchers
Campaign:readRead scheduled price campaigns
These cover currency and country values that appear on prices, totals, addresses, markets, and pricelists.
PermissionWhat it unlocks
Currency:readRead currencies on prices and totals
Country:readRead countries on addresses, markets, and pricelists
The full read baseline, ready to copy:
Read permissions
Product:read
ProductVariant:read
ProductSize:read
Brand:read
Collection:read
Display:read
Bundle:read
Warehouse:read
ProductVariant.stock:read
ProductSize.stock:read
Order:read
Order.shippingAddress:read
Order.billingAddress:read
Return:read
Customer:read
Customer.billingAddress:read
Market:read
Store:read
Pricelist:read
Category:read
Voucher:read
Campaign:read
Currency:read
Country:read

Write access (optional)

Add these only if you want the agent to make changes in Centra. Write tools run only when you ask, and Dema prompts you to approve sensitive changes before they are applied.
PermissionWhat it unlocks
StockChange:write + WarehouseDelivery:readSet or correct stock quantities
PermissionWhat it unlocks
Order:writeConfirm or cancel orders
Purchaser:readRequired to cancel an order
OrderHistory:writeAdd notes to an order
Shipment:write, Shipment:read, Shipment.shippingAddress:read, AdminUser:read, StorePlugin:readCreate shipments and fulfil orders
PermissionWhat it unlocks
Product:writeUpdate product fields (name, status, number, internal comment)
Customer:writeUpdate customer fields (status, internal comment)
Attribute:writeSet custom attributes (custom fields) on any object
PermissionWhat it unlocks
Category:writeCreate categories and add or remove displays
PermissionWhat it unlocks
Price:writeSet a product’s price in a pricelist
Voucher:writeDisable or delete vouchers
Creating a shipment also requires AdminUser:read and StorePlugin:read on the token — Centra needs them to resolve the shipping configuration even though the agent never reads that data directly.
The write permissions, ready to add on top of the read baseline:
Write permissions
StockChange:write
WarehouseDelivery:read
Order:write
Purchaser:read
OrderHistory:write
Shipment:write
Shipment:read
Shipment.shippingAddress:read
AdminUser:read
StorePlugin:read
Product:write
Customer:write
Attribute:write
Category:write
Price:write
Voucher:write

When your token expires

Centra Integration API tokens are static and expire on the date you set (30 days by default). When a token expires, the integration shows as expired in Dema and the agent stops using it. To restore access, create a fresh token in Centra and paste it in via Reconnect on the integration card.
Set a calendar reminder a few days before the expiry date so the agent never loses access unexpectedly. A longer expiry window means fewer rotations, at the cost of a longer-lived credential — pick what fits your security policy.

Troubleshooting

Centra names the exact permission in the error (it returns permissionsUsed on every request). Open the token in System → API Tokens, add the named permission, save, and click Reconnect in Dema. If the token cannot be edited, create a new one with the added permission and reconnect.
The Account URL must be an HTTPS URL pointing at your Centra store, in the form https://your-store.centra.com. Use your real store hostname, not a hand-written value.
Your Centra token reached its expiry date. Create a new token in Centra and click Reconnect on the Centra integration card to paste it in.
Make sure you granted the matching write permission when you created the token (see Write access). Write permissions are not included in the read baseline and must be added deliberately.
If you are still stuck, contact support with the error message you see.

Additional resources