Skip to main content

Overview

Once Ongoing WMS is connected, the Dema Agent can pull live warehouse data for a goods owner directly inside a conversation — article data, stock balances, and warehouse information. The agent only acts when you ask it to.

Prerequisites

  • An Ongoing WMS account with administrator access, so you can create an integration user for a goods owner.
Ongoing WMS does not use a sign-in (OAuth) flow. You create an integration user in the Ongoing admin, and Ongoing generates the two values you paste into Dema — an API URL and an Authorization header. Copy both exactly as shown.

Connect Ongoing WMS

1

Create an integration user in Ongoing WMS

  1. In Ongoing WMS, go to Administration → API for goods owners.
  2. Select the goods owner the agent should access.
  3. Click Add new user for AI tool integrations.
  4. Ongoing generates an API URL and an Authorization header value for that goods owner. Copy both.
The API URL looks like https://api.ongoingsystems.se/{warehouse}/api/v1/mcp, where {warehouse} is your system name. Use the exact URL Ongoing shows you.
2

Connect in Dema

In Dema, go to Agents → Settings → Integrations, find Ongoing WMS, and click Connect. Enter:
  • MCP URL — the API URL Ongoing generated.
  • Authorization header — the Authorization header value Ongoing generated. Paste it exactly as given, including any prefix.
Click Add. Dema marks the integration as Active.
One credential connects one goods owner. To give the agent access to another goods owner, create a separate integration user in Ongoing and add it as another connection.

Troubleshooting

Paste the Authorization header value exactly as Ongoing generated it — do not trim or change it. If you are unsure, create a fresh integration user under Administration → API for goods owners and copy the new values.
The MCP URL must be the API URL Ongoing generated for your goods owner, on api.ongoingsystems.se. Copy it directly from the Ongoing admin rather than typing it by hand.
If you are still stuck, contact support with the error message you see.

Additional resources