Want's to ingest data to Enterspeed – products from your PIM, orders from your ERP, content from your CMS. Now you can wire that data into automated workflows without writing a single line of glue code. ⚡

We're excited to announce the official, verified Enterspeed node for n8n – the workflow automation platform that connects 1000+ apps and services. With the Enterspeed node, you can push data into Enterspeed and pull it back out as part of any automation, all from n8n's visual canvas.

It's available now, so go ahead and give it a try.

Why it matters

n8n is where teams stitch their tools together – triggering flows on a schedule, reacting to webhooks, and moving data between systems. Adding Enterspeed to that mix means you can automate the unglamorous parts of your data supply chain: sync a product feed on a timer, ingest CMS changes the moment they happen, or fan data out to downstream systems – no custom scripts, no maintenance burden.

And because it's a verified community node, it's vetted by n8n and installable straight from your instance.

The node supports everything our REST API does, so anything you can do outside n8n, you can now do inside it.

What you can do

Ingest

• Save – ingest or update a source entity
• Delete – remove a source entity permanently
• Bulk save – ingest or update up to 50 source entities in one call
• Bulk delete – delete up to 50 source entities in one call

Delivery

• Get content – retrieve a view by URL, ID, or handle

Query

• Query Items – query a single index
• Multi Query Items – run up to 5 queries in a single request

Route

• Get Many – retrieve a list of routes for the environment

A quick example

Imagine a nightly workflow: an n8n Schedule trigger fires → an HTTP Request node pulls the latest product from your PIM → the Enterspeed node does a Bulk save. Your Query API stays fresh, and your PIM stays offloaded – all on autopilot. 🚀

Getting started

Check out the Enterspeed n8n node and n8n's guide on installing verified community nodes. Full details are in the Enterspeed n8n documentation.

Questions? Reach out on our support Slack channel or at support@enterspeed.com.

You've been able to ask questions about your data with the Query MCP. Now you can ask about your tenant too. 🛠

The new Enterspeed Management MCP turns the Enterspeed Management API into a set of Model Context Protocol (MCP) tools that AI clients like Claude, Cursor or VS Code can discover and call on their own. Where the Query MCP reads your data, the Management MCP reads – and changes – your configuration: sources, environments, domains, clients, and the mapping schemas that tie it all together.

It's available now, so go ahead and give it a try.

Why it matters

For a long time we've had the Enterspeed CLI to read or configure a tenant from code, and while the Management MCP can do more or less the same, it's more tailored to agents. Now you can simply ask: "Give me an overview of my tenant", "What triggers the schema behind my product pages?" or "Show me any processing errors in the last 24 hours". You can even have an agent author a mapping schema, dry-run it against a real source entity, and save a new version, all in one conversation.

Read more in the Enterspeed Management MCP documentation.

Nobody types perfectly. A shopper searching your site will mistype "televisiom", drop a letter, or add one too many – and until now, that meant no results.

The Enterspeed Query API now supports fuzzy search, so small typos no longer return an empty result. Instead of demanding an exact match, it finds the closest results and ranks them by relevance – giving people what they're looking for, even when they don't spell it quite right.

It's a natural fit for search bars, autocomplete, and anywhere your users type freely. Fuzzy search works on analyzed text fields in your index and can be combined with your existing filters, sorting, pagination, and facets.

A quick example

Request – note the deliberate typo in televisiom:

POST https://query.enterspeed.com/v1/productIndex

{
  "search": {
    "field": "name",
    "value": "televisiom",
    "literal": false
  }
}

Response – the correct item still comes back, ranked by _score:

{
  "status": 0,
  "totalResults": 1,
  "results": [
  {
    "sku": "p-5427",
    "name": "Television",
    "url": "/products/television/",
    "_score": 1.389
  }
  ]
}

Try it in the Management App

Search is also available directly in the Query playground in the Management App – no code required. Build and tweak your query, hit run, and see results instantly.

And as a nice extra: once you've built your query, you can now just click the cURL button to copy the full cURL request based on your query. 🚀

Check out the full details in the Query API documentation.

Your data already lives in Enterspeed – products from your PIM, orders from your ERP, customers from your CRM. Until now, getting answers out of it meant writing queries. What if you could just… ask? 🤔

That’s exactly what the new Enterspeed Query MCP unlocks. It turns the Enterspeed Query API into a set of Model Context Protocol (MCP) tools that AI clients like Claude, Cursor or Azure AI Foundry can discover and call on their own – answering questions in plain English, grounded in your real data across multiple sources.

The Enterspeed Query MCP is now available in public preview, so go ahead and give it a try.

Why it matters

AI is only as good as the data behind it. Enterspeed already does the unglamorous part – connecting your backend systems into one clean, structured, fast data layer. The Query MCP simply opens that layer to AI clients in a governed way: scoped keys, index restrictions and read-only access, all enforced by the Query API.

So no more pinging a developer for a one-off BI query or HTTP endpoint every time you need a specific answer. Merchandisers and analysts can just ask – no system logins, no query language, only read-only access to the data already in Enterspeed.

Read more and see a concrete commerce example in the Enterspeed Query MCP blog post or checkout the documentation.

If you've been building with Enterspeed  –  it means you know better than anyone what works, what doesn't, and what's missing.

We're working on the next major version of the platform, and before we lock in direction, we want to hear from the people actually using it. 

The survey takes about 5 minutes, and your answers will directly influence what we build next.

[Take the survey →]

Oh, and everyone who completes the survey is entered into a draw for an Enterspeed hoodie. 💙 (Just leave your name at the end – we'll only use it for the draw.) 

Brutal honesty welcome 😬

We wanted to give you a heads-up that the global search feature in the Enterspeed Management App — powered by CommandAI's Spotlight — will be discontinued later this month (June 2026).

The reason is twofold: CommandAI is ending support for the Spotlight feature, and looking at our usage data, only a small number of users have been using it regularly.

We know it's a handy feature for navigating the Management App, but based on the low usage and the loss of support, we've decided not to build an alternative — at least for now.

We're sorry for any inconvenience this may cause, and as always, feel free to reach out if you have any questions.

Are you working with large number of entities, being customer specific prices or entities that changes often like e.g. inventory numbers?

Up until now Enterspeed has had its strength on static data from a CMS, a PIM system or something similar. This is because the way Enterspeed preprocesses the data making it stable and fast to fetch on the client.

But no approach is the perfect solution for all use cases, and we know that not all data is static and requires transformations. So, why put data through a transformation process that takes a lot of resources if the data doesn’t need transformation or if it’s never even being fetch by the client?

That’s why we added a new type of data flow in Enterspeed called Auto Indexing.

It’s a feature you enable on the Source group. Once it’s enabled all the data you ingest into this Source group will automatically be added directly to an Index you can query from the Query API.

The new Auto Indexing mode lives comfortably together with the existing schema transformation mode, given you the options to use whatever mode is the best for your specific data set and often it will be a combination of both for your project.

When using Auto Indexing you don’t have the option to create schemas for the source entities, so you can’t do transformation on the data. But instead, you can ingest a large volume of data and have frequently changes to the data making it perfect for dynamic data like customer specific prices or inventory numbers. And especially in combination with the bulk Ingest API you can really send some data through to Enterspeed and have a fast and flexible Query API to fetch the data and offload your ERP system or wherever your data is coming from 🚀

Head over to your Enterspeed tenant today and start using the now Auto Indexing mode and if you need more information, check out the documentation about Auto Indexing.

🚀 The Query API .NET SDK has been updated with a completely new syntax.

We've rebuilt the SDK around a fluent QueryBuilder API. Queries are now constructed in a way that feels natural in .NET – type-safe, chainable, and with full IntelliSense support. If you're on the previous version, it's worth upgrading.

What's new

• Fluent QueryBuilder API – chain filters, sorting, pagination, and facets in a single expressionTyped query builders – use your own C# models to drive queries; property names are automatically camelCased, or mapped via [JsonPropertyName]
• Lambda-based filtering – reference model properties directly instead of magic strings
• Nested logical grouping – compose complex AND/OR filter trees with ease
• ISuccess / IFailure result handling – no more silent failures or unchecked nulls
• Non-typed builder still available – if you prefer to work without generics

Getting started

1. Install or update the NuGet package
2. Register the service:
   services.AddEnterspeedQueryService()
3. Start building queries – check the GitHub repo for full docs and examples

We've added a safeguard to prevent accidental type changes that could break your content delivery.

What changed

The Ingest API will now reject requests that attempt to change the type of an existing source entity. If you re-ingest a source entity with a different type than what was originally stored, you'll receive a 422 validation error.

Why we made this change

When a source entity's type changes, any routes or views bound to that type become stale — potentially breaking content delivery without warning. This guard makes type mismatches fail loudly rather than silently, giving you immediate visibility into the issue.

What you need to do

In most cases, nothing. This guard only triggers if your ingest pipeline is attempting to change the type of an entity that already exists.

If you see the error and the type change is intentional, you have two options:

1. Delete the entity first — Remove the source entity via the delete endpoint, then re-ingest with the new type. This is the recommended approach as it properly invalidates dependent routes and views.
2. Use the bypass header — Include the X-Enterspeed-Force-Type header in your ingest request to override the protection. Only use this if you're certain the type change won't cause downstream issues.

Example error response

If you encounter this unexpectedly, it likely indicates a data inconsistency in your ingest pipeline that's worth investigating.

Questions or concerns? Reach out to us on our support Slack channel or at support@enterspeed.com — we're happy to help.