---
title: How do we build a plugin in Tool Studio? | Build EmployeeWorks plugins with ToolSmith (Part 3)
date: 2026-10-30
abstract: Before ToolSmith builds a plugin for you, it helps to know how plugins are put together so you can review its plan. The third video in the Build EmployeeWorks plugins with ToolSmith series walks through a plugin's assets in Tool Studio (connector, HTTP actions, conversational process and the plugin itself), then follows an employee's request through all of them.
tags: ServiceNow, EmployeeWorks, ToolSmith, Tool Studio, AI, Agentic AI, Developer Experience
author: Chris Reddington
canonical_url: https://chrisreddington.com/video/how-do-we-build-a-plugin-in-tool-studio/
---


This is the third video in the Build EmployeeWorks plugins with ToolSmith series on the ServiceNow Dev Program channel. The video covers the following topics:

- Why knowing how plugins are put together helps you review ToolSmith's plan and understand what it's building
- Connectors, which hold the travel system's base address and authentication settings
- HTTP actions, the API requests sent to that system (one finds bookings, another requests cancellation)
- The conversational process, which identifies the booking, asks for confirmation and then requests cancellation
- Slots, which hold the record a process needs (a bit like a parameter), and resolvers, which turn natural language into one specific record
- The plugin itself, with a natural-language trigger that uses example requests to recognise when it fits, and a launch configuration that sets who can use it
- Following an employee's request from the AI Assistant selecting the plugin to the result coming back

The full written series is on the [ServiceNow Community](https://www.servicenow.com/community/sn-employeeworks-blog/build-employeeworks-plugins-with-toolsmith/ba-p/3613461).