Skip to main content

​
Overview

Once Nosto is connected, the Dema Agent can work with your Nosto data directly inside a conversation — browse your product catalog, look up individual products, list customer segments, pull account-level affinity insights (top brands, categories, and product types), fetch product recommendations such as best-sellers and related items, and look up individual orders. All access is read-only — the agent never changes anything in your Nosto account. The agent only acts when you ask it to.

​
Prerequisites

  • A Nosto account with access to Settings → Authentication Tokens — you may need an admin on your account to open this page.
Nosto has several token types. Dema needs the Apps token from Settings → Authentication Tokens. A public token only covers a subset of the API and will not work for everything the agent does.

​
Connect Nosto

1

Copy the Apps token in Nosto

  1. In Nosto, go to Settings.
  2. Open Authentication Tokens.
  3. Find the Apps token and copy it.
2

Connect in Dema

In Dema, go to Agents → Settings → Integrations, find Nosto, and click Connect. Enter:
  • Nosto Apps API token — the Apps token you copied from Nosto.
Click Add. Dema marks the integration as Active.
A single Apps token covers everything the agent does — no other credentials or account identifiers are needed.

​
Rotating the token

To rotate the token, regenerate the Apps token in Nosto under Settings → Authentication Tokens, then click Reconnect on the Nosto integration card in Dema and enter the new token.

​
Troubleshooting

Check that you copied the full Apps token from Settings → Authentication Tokens. Other token types — such as the public token — will not authenticate correctly here.
The Settings → Authentication Tokens page may be restricted on your account. Ask an admin on your Nosto account to copy the Apps token for you, or to grant you access.
Confirm the Apps token has not been regenerated or revoked in Nosto. If it has, copy the current token and click Reconnect in Dema.
If you are still stuck, contact support with the error message you see.

​
Additional resources