Skip to main content
Let your assistant read prices, stock and order statuses from your Shopware 5 shop. It never changes anything in the shop.
Shopware 5 no longer receives security updates: security support ended on 31 July 2024, and the last release was 5.7.20. Plan your move to Shopware 6. This connection is for shops that still run Shopware 5 in the meantime.

Set up your shop

  1. Check the version. The connection needs Shopware 5.3.2 or later and is tested with 5.7. Your shop must be reachable over HTTPS from the internet.
  2. In the Shopware backend, open Settings → User administration, edit a backend user and open API access. Turn on API access and copy the API key.
  3. Give that user read rights for articles and orders only, through its role. The assistant can read everything this user can read.
  4. In Famulor, open Agent Tools → Marketplace → Shopware 5. Enter the shop address, for example https://shop.example.com (add the subfolder if the shop runs in one), the API user name and the API key. Leave Shop time zone empty to use Europe/Berlin.
  5. Choose Add. The connection is checked before it is saved. Then assign the connection to your assistant.
To change the address or the credentials later, remove the tool and connect again.

What the assistant can do

Both tools are enabled by default. Switch them off under Edit.
  • Search products: finds products by name or article number and tells the caller the price including VAT for standard customers, the stock and whether a product has variants. If a product has no tax rate stored, the assistant does not name a price.
  • Order status: tells the caller the status, the payment status, the contents, the total, the shipping method and whether a tracking number exists for one order.
Status names come from your shop’s own order and payment statuses. A status you created yourself is read out as you named it.

Order privacy

The caller names the order number. The assistant asks for the e-mail address used for the order or the delivery postcode and shows the order only when it matches. The order number alone is never enough. A wrong detail and an unknown order number get the same answer, so nobody learns whether an order exists. After three wrong attempts for the same order number the assistant stops checking that order. The assistant never reads out addresses, e-mail addresses, phone numbers, comments or tracking numbers.

What it does not do

  • It does not change anything: no orders, statuses, notes or customers. Read rights are enough for the API user.
  • It does not recognise callers before the conversation starts.
  • It does not look up an order by phone number alone.
  • It does not read out tracking numbers. It only says whether one exists.
  • It does not support Digest authentication.

Test safely

The connection only reads, so a test cannot change your shop. Test with an order of your own: give the order number and the e-mail address of the order. Check that a wrong postcode gets the same answer as an unknown order number.

Channels

On every channel the assistant asks for the e-mail address or the delivery postcode.

Automations

Connect Shopware 5 under Automations → Connections, or import its Agent Tool connection. Both tools are available as actions. An automation started by a call or a text conversation (SMS, WhatsApp) knows the other party’s number from that call itself. Other runs (webhook, schedule) have no caller, so Order status always needs the e-mail address or the delivery postcode there.

API, MCP, CLI & SDK

POST /api/v1/tools/integrations/shopware5 · MCP connect_integration · CLI famulor connect-integration shopware5. client.api.connectIntegration needs famulor-sdk 0.2.12 or later. Update the CLI with npm install --global famulor before you use connect-integration.

Troubleshooting

  • “This looks like a Shopware 6 shop”: you entered the address of a Shopware 6 shop. Use the Shopware 6 connection instead.
  • “Shopware rejected the API user or key”: check the user name and copy the API key again. Make sure API access is turned on for that user.
  • “The API user needs read rights for articles and orders”: open the role of the API user and allow reading articles and orders.
  • “This address does not lead to the Shopware 5 API”: check the address. If the shop runs in a subfolder, include it. Do not add /api.
  • “The shop answered with a web page instead of data”: a firewall, a security plugin or a maintenance page blocks the request. Allow requests to /api for the connection.
  • “This address redirects to another address”: the shop forwards visitors, for example from the address without www to the one with www. Enter the address the shop really uses.
  • “The shop refused the API request”: a firewall or security module (for example mod_security) blocks /api. Allow requests to /api for the connection.