Skip to main content
Community Manager
Nov 18, 2026 10:02 PM UTC

Catalog Interpreter FAQ

Catalog Interpreter FAQ

Catalog Interpreter lets your admins turn ServiceNow catalog items and record producers into conversations, so employees complete those forms by chatting with the Moveworks assistant. This FAQ covers how the product works, which forms it converts, what the controlled availability (CA) program involves and what your environment needs.

The product

  • What is Catalog Interpreter?

    Catalog Interpreter (CI) converts a ServiceNow catalog item or record producer into a conversational Moveworks plugin. Each converted form becomes one Tool Studio plugin with a natural-language trigger. The plugin checks that the employee may order the item, collects the form's fields in chat, and files the request in ServiceNow.

  • What problem does Catalog Interpreter solve?

    Classic in-bot form filling depends on mirrored form configurations, which limits how many forms work in chat, and hand-built conversational forms take hours per form with no way to keep them in sync with ServiceNow.

    Catalog Interpreter lets your admins convert forms self-serve, and it flags converted forms whose ServiceNow source has changed.

  • How does a conversion work?

    1. The Catalog Interpreter app is installed on your ServiceNow instance, by your ServiceNow admin or by Moveworks from Forms setup in Tool Studio.
    2. An admin opens the Forms page in Tool Studio, picks an eligible form and clicks Convert.
    3. The interpreter plans the plugin, asks the admin about anything the form leaves ambiguous, and builds the plugin once the admin approves the plan.
    4. The admin tests the plugin in chat before sharing it with employees.

    After conversion, admins can fine-tune the plugin in Tool Studio using Toolsmith or manually.

  • Can admins convert many forms at once?

    Yes.

  • Do admins use a UI or a command-line tool?

    A UI. Admins convert forms on the Forms page in Tool Studio.

  • Does the admin review a conversion or answer questions during it?

    Yes. Each conversion pauses until the admin answers the interpreter's questions and approves the plan. After conversion, admins can fine-tune the plugin in Tool Studio.

  • What happens when someone changes a converted form in ServiceNow?

    ServiceNow tells Catalog Interpreter the form changed, and the Forms page shows what changed. The admin clicks Convert again to update the plugin; nothing updates automatically. The existing plugin keeps working until the admin converts again, and converting again starts the admin's answers from scratch.

  • We already have conversational forms built in Tool Studio. Will Catalog Interpreter maintain them?

    No. Catalog Interpreter cannot see plugins built before it, so their updates stay manual. To bring a form under Catalog Interpreter, convert the ServiceNow form with Catalog Interpreter once it is available to you.

  • How is Catalog Interpreter different from other ways to fill forms with Moveworks?

    • EmployeeWorks web app: opens the real ServiceNow form next to the chat, and the employee fills it by hand. Web only.
    • Classic in-bot forms: Moveworks mirrors form configurations, which limits how many forms work in chat.
    • Catalog Interpreter: a generated plugin collects the form through conversation in chat.
  • Will employees see a form or a conversation?

    A conversation, if that form has been converted. Forms that have not been converted keep the usual form experience.

  • Who shows as the requester in ServiceNow, and what happens after submission?

    The employee. The employee must match an active, non-admin ServiceNow user by email. After submission, your existing ServiceNow workflow, including any approvals, runs as usual.

  • Will Catalog Interpreter make every form fillable in chat, or clean up messy catalog items?

    The goal is to convert every catalog item. Some forms will produce unideal experiences, and some will hit technical blockers (see "What stops a form from converting?"). Catalog Interpreter converts each form as built, so a confusing form may produce an underperforming conversation.

  • Does Catalog Interpreter prefill fields the assistant already knows?

    Partly. ServiceNow's own defaults, such as Opened For set to the submitter, apply because the request runs as the employee. The assistant also fills what it can from the employee's request.

  • Can an admin test a converted form before employees see it?

    Yes. A new plugin is published only to the admin who converted it, and the admin tries it in test chat before sharing it.

  • Can a converted form be a Smart Handoff option?

    Only on the Agentic Orchestrator, which lets you describe your own handoff options, including filling a form with Catalog Interpreter. The classic assistant's Smart Handoff offers fixed forms only.

  • Can a converted form run an automation with no conversation, such as a webhook-triggered agent?

    No. Catalog Interpreter generates conversational plugins only.

Eligibility: which forms convert

  • Which ServiceNow form types can Catalog Interpreter convert?

    Catalog items and record producers. Order guides are unsupported.

  • What do we install in ServiceNow?

    The Catalog Interpreter scoped app. The app is distributed through ServiceNow's Innovation Lab release, ServiceNow's controlled release for apps before GA, with each customer's install approved individually. Install instructions are provided during CA onboarding.

  • Does Catalog Interpreter convert every form, or does the customer choose?

    You choose. The app installed in ServiceNow reads the whole catalog, and an admin picks which forms to convert. The rest keep the usual form experience.

  • What stops a form from converting? Does the admin see why?

    Known blockers (the list is not final):

    • A field with no chat equivalent, such as a complex multi-row variable set or a widget
    • A script include in a private scope
    • An attachment-only form
    • A script that reads the browser page, or an encrypted script
    • An order guide

    The Forms page lists each blocked form with its reason.

  • Which ServiceNow variable types does Catalog Interpreter support?

    • Supported: single-line text, wide single-line text, multi-line text, email, URL, IP address, checkbox, yes/no, multiple choice, select box, lookup select box, lookup multiple choice, list collector, reference, requested for, date, date/time, duration, numeric scale, masked, table name and attachments.
    • Blocks conversion: widgets,custom, custom with label, UI page and complex multi-row variable sets.
    • Ignored: label, rich text label, HTML and layout elements.
  • Are catalog widgets supported?

    No. Widgets (custom, custom with label and UI page variables) block conversion, and no widget support is scheduled.

  • Are catalog client scripts and script includes supported?

    Mostly yes.

    • Client scripts: Catalog Interpreter rewrites them into the plugin.
    • Script includes: the plugin calls them through the Catalog Interpreter app after a ServiceNow admin approves a cross-scope grant at conversion.
    • Blocks conversion: a script include in a private scope, a script that reads the browser page (document, window, gel) and an encrypted script.
  • Are UI policies, catalog data lookups and reference qualifiers supported?

    Mostly. The Catalog Interpreter app reads UI policies, choices and reference qualifiers into the form definition, and simple dependent dropdowns convert well. Scripted reference qualifiers cannot run inside the plugin.

  • Does a converted form respect user criteria (Available For / Not Available For)?

    Yes. The plugin checks that the employee may order the item before the conversation starts, and ServiceNow checks again at submission, as the employee.

  • Does the admin see a complexity score?

    Yes. The Forms page shows Low, Medium or High for each convertible form, which signals how much admin input the conversion needs. Admins can convert at any level, and blocked forms still show their reason.

  • Can Catalog Interpreter convert a form that ServiceNow marks as non-conversational?

    Yes, unless the form hits one of Catalog Interpreter's blockers. Catalog Interpreter ignores ServiceNow's conversational rating. The most common reason ServiceNow gives, a catalog client script, does not block Catalog Interpreter.

  • Does Catalog Interpreter work for Jira, Freshservice or other non-ServiceNow forms?

    No. Catalog Interpreter converts only ServiceNow catalog items and record producers. Forms in other systems link out to that system's portal.

  • Can employees submit a converted form on behalf of someone else?

    No.

  • How should we design forms so Catalog Interpreter converts them well?

    Simpler forms produce shorter conversations with fewer errors. Avoid the blockers listed under "What stops a form from converting?"

  • Does CA roll out in phases?

    Yes. The first cohort of customers is set. Timing for a later phase is not decided yet, so ask your account team to register your interest or head to this link for self-nomination: https://community.moveworks.com/p/catalog-interpreter-controlled-availability

  • How many forms does each customer convert in CA?

    Each customer converts a suggested 5 to 7 forms during self-service, starting with the highest-volume or highest-impact forms.

  • What does a CA customer commit to?

    • ServiceNow Australia release or later, and access to a Moveworks sandbox.
    • A champion and a developer who can change the ServiceNow instance.
    • Picking forms, granting API access and testing converted forms in chat.
    • Meetings 3 times a week for the first 2 weeks of self-service, then weekly, plus an exit feedback meeting.
  • Who supports CA customers?

    The Catalog Interpreter product team is your primary contact, with regular meetings and a feedback document per customer. Once self-service is live, issues go to Moveworks Product Support.

  • Can we get Catalog Interpreter before CA starts?

    No. Every CA customer gets access on the CA start date.

Eligibility: customers and environments

  • Which ServiceNow release do we need?

    Australia or later. Catalog Interpreter needs its ServiceNow app on the instance, and the app requires Australia.

  • Does Catalog Interpreter work on the classic assistant?

    Yes. Catalog Interpreter is available across all channels and works with any reasoning engine version.

  • What setup does the Moveworks side need? Is training required?

    In Forms setup in Tool Studio, the admin picks the ServiceNow connector, and Moveworks checks the instance for the app, installs it on request and creates the Catalog Interpreter connectors. No training is required.

  • Do we need EmployeeWorks?

    No. Catalog Interpreter runs without EmployeeWorks but works better with it.

  • Does Catalog Interpreter work through the Conversations API?

    Yes.

  • Which regions is Catalog Interpreter available in?

    During CA, the conversion service runs in the US region. Other regions (EU, Canada, UK, Japan and Australia) follow shortly after the CA start on December 17, 2026.

  • Does Catalog Interpreter work if we reach ServiceNow through the on-prem agent or an IP allowlist?

    Not yet. Moveworks reaches the Catalog Interpreter app over OAuth from Moveworks servers.

  • What customer data does Catalog Interpreter read and store?

    The Catalog Interpreter app reads every catalog item and record producer on the instance. For each form it reads the form logic (variables, UI policies, client scripts, choices, reference qualifiers) and request volume, and no server-side script bodies. Moveworks stores each form's logic and volume in its own database.