Quickstart
Learning Objectives
In this quickstart, you'll learn to configure your first Query. We will use an API based on a publicly available holiday API to look up the public holidays through your bot.
Before you start, make sure...
- You have the access to the Queries Workspace.
Step 1: Create a New Query
- Go to Queries Workspace
- Click
Create
. - Enter a name and description. Feel free to copy from below:
Name
2023 Holiday Calendar
Description
🎄 Lookup the list of public holidays for 2023.
test
, demo
, etc.)
Do not enter placeholder values (These values will be
- Shown directly to your users
- Used to build the generative intent
Using poor names will result in a poor chat & NLU experience.
Step 2: Setup Your API Request
In this step, you will teach Queries how to interact with your APIs.
- Select the pre-configured
Creator Studio Sample Endpoints
connector. This contains any relevant authentication + connection information for your API, along with a base url (https://us-central1-creator-studio-demo.cloudfunctions.net
in this case)Missing connector?
If you do not see the
Creator Studio Sample Endpoints
connector, work with your Moveworks Customer Success team to register a new connector. - Fill in the "API endpoint" path for the holiday calendar api, which is
/holidays
. This gets appended to the connector's base URL.Do not put query parameters in the path.
Some APIs have query parameters in the URL path. Please enter these in the query parameters table.

- Select
POST
under the "Method" section.

- Paste the following text in the "JSON request body" section (leave the "headers" and "query parameters" sections empty).
{ "year": 2023 }

- 🎉 Your API Endpoint is setup! You can see our API configuration guide for advanced setup details
Step 3: Label the API Response
In this step, you will teach Queries how to present the API information to users.
Based on your instructions, Queries will perform response synthesis on the API data to design the final message to the user.
- Specify the
root element
. This is the key to either thelist
of records lives, ordictionary
containing the individual record retrieved by the API.In the following snippet,
data.holidays
is the root element.{ "data": { "holidays": [ { "name": "Holiday 1", "date": "Date 1" }, ... ] } }
- Map the
identifier
. This is the most obvious "title" for a given record, something that a user would use to uniquely identify the record.For a holidays query, let's use the
name
. - Map the
description
. This is a "primary" attribute. Especially if the identifier is an alphanumeric ID, the description is helpful to contextualize what the record is.For a holidays query, let's use the
date
. - You can leave "Additional Info" blank for now, but you can label other attributes that Moveworks can use in response synthesis.
For example, the
global
key refers to if the Holiday is aWorldwide Holiday
.

- Add a button to link users to a website listing the public holidays for the year.
Button Name
View Holidays
URL
https://date.nager.at/PublicHoliday/Country/US
- 🎉 Your API response is labeled. For best practices & advanced details, see our response synthesis guide
Step 4: Generate Your Intent
In this step, you will teach Queries when to present data to your users.
- Choose
This lookup doesn't contain any keyword
.
Since this query will always return the holidays for 2023, there are no slots. You can learn more about slot extraction configuration options here.
- Add at least 3 ways to ask about this query.
Temporary Step
This only applies to our pre-launch customers, we will automate the generation of these utterances based on the API schema by our public launch.
For this use case, we can use
show upcoming vacations
- a "command-line" utteranceWhat holidays do we have in 2023
- a "general utterance"When is MLK day?
- a "sample record" utterance
If you need help coming up with these, see our intent tuning tips
Step 5: Control Access & Launch
- Choose
Launch to selected emails(Testing)
- Add your work email address under Allow Emails Values
- Click Launch.
Do not use this endpoint in production.
Our team publishes test endpoints for your experimentation as part of the
Creator Studio Sample Endpoints
connector. These are not stable APIs designed for production use across your entire company.
Do not attempt to edit the Query.
If you need to make changes to your Query, please exit Creator Studio first, otherwise you may produce duplicate Queries.
You can learn more about the other launch management options here.
Step 6: Test!
A few minutes after launching, you can test your new Query in chat!
Try a complex utterance like the one shown below. Even though it looks nothing like the original queries, it still works great!

Read more about why this works with our generative intents!
🎉 Congrats! Now, make it more powerful
When combined with the right complimentary technologies, you can accomplish incredible things with Queries.
- Learn to Extract user-provided values (slots)
Not sure where to start? Check out our Idea Library for the touch of inspiration you need!