# Jitbit MCP connector Connecting Jitbit to Elaichi lets Claude, ChatGPT, Cursor and the Elaichi Agent search, create, update, merge and close Jitbit tickets inside each person's own help desk access, with every action written to an audit log. Source: https://elaichi.ai/connectors/jitbit/ ## Facts | | | | --- | --- | | Application | Jitbit | | Category | Helpdesk | | AI tools | 64 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. 64 tools is past the 30-tool threshold, so clients use `search_tools` and `execute_tool` | ## What you can ask once Jitbit is connected - Show open Jitbit tickets assigned to me this week - Close the duplicate Jitbit tickets linked to ticket 4821 - Which Jitbit tickets have no assignee since Monday ## Connect Jitbit in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Jitbit. 2. Optionally set Share with, then press Connect. 3. Paste a Jitbit API key. One person generates a token in Jitbit and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Jitbit tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Jitbit to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Jitbit to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Jitbit to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Jitbit to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Jitbit tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Jitbit through Elaichi ### Log a ticket straight after a call Support. Describe the problem in plain words and the agent creates the Jitbit ticket, sets the priority and fills in the custom fields, so nothing waits until the end of the shift. ### Merge duplicate tickets about one outage IT. When the same printer or VPN failure lands as five tickets, ask the agent to find them, merge them into one and tag it, so the fix is tracked in a single place. ### Pull in a second pair of hands Support. Add a secondary assignee to a stuck Jitbit ticket and link it to the related ones, so the colleague picking it up sees the whole thread of the problem. ### Break a big request into subtickets Operations. Turn a new hire setup or office move into a parent ticket with subtickets for each piece of work, then check which subtickets are still open. ### Review a company's open tickets before a call Customer Success. Ask what is still unresolved for a particular company in Jitbit, with priorities and attachments, and walk into the renewal conversation already knowing the answer. ### Check the help desk numbers each morning Team leads. Ask for the current Jitbit stats, open tickets by priority and anything that has sat untouched, then close out what has been resolved without opening the queue. ## Frequently asked questions ### How do I connect Jitbit to Claude? Connect Jitbit in Elaichi first: paste in a Jitbit API key when asked, and the connection is ready. There is no OAuth application to register in Jitbit and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and from then on it can work with your Jitbit tickets. ### Does Jitbit work with ChatGPT and Cursor as well as Claude? Yes. Once Jitbit is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Jitbit once and every client you use picks it up. ### What can an AI agent actually do with my Jitbit data? It can search and read Jitbit tickets, create new ones, update them, set priorities and custom fields, add tags, assign a second person, link related tickets, merge duplicates, build parent and subtickets, close tickets and read attachments. It can also list your companies and pull the help desk stats for a quick status check. Because Jitbit brings a lot of actions, short concrete asks like "close ticket 4821" work better than long paragraphs. ### Does connecting Jitbit give the AI access to every ticket in the help desk? No. Each person signs in to Elaichi as themselves, so an agent working with Jitbit only sees the tickets, companies and fields that person's own Jitbit access allows. Elaichi can narrow that further with restrictions, and it can never widen what Jitbit already permits. ### Can my team share one Jitbit connection? Yes. One person connects Jitbit with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who created, updated or closed each Jitbit ticket. ### Can I stop an agent from deleting or changing things in Jitbit? Yes. Restrictions in Elaichi work per action, so you can allow reading and searching Jitbit tickets while blocking closing, merging or editing them. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it. ### What happens to a Jitbit connection when someone leaves? Offboarding that person in Elaichi ends their access to Jitbit through every client at once. If they had shared a Jitbit connection with a team, it keeps working for everyone else. If you want Jitbit gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ## All 64 Jitbit tools Every tool below is callable through https://api.elaichi.ai/mcp once Jitbit is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Jitbit authorization** (List). Test Jitbit authentication by verifying the current user's credentials. Returns the authenticated helpdesk user object including UserID, Username, Email, FirstName, LastName, IsAdmin, IsTech, IsManager, and LastSeen. - **List all Jitbit tickets** (List). List Jitbit helpdesk tickets with optional filters by category, status, date, assignee, tag, and more. Returns: UserName, FirstName, LastName, UserID, CompanyID, CompanyName, Email, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Max 300 per page. - **Get single Jitbit ticket by ID** (Get). Get details of a single Jitbit ticket by id. Returns: Attachments, Tags, Status, OnBehalfUserName, SubmitterUserInfo, CategoryName, AssigneeUserInfo, TicketID, UserID, AssignedToUserID, IssueDate, Subject, Body, Priority, StatusID, CategoryID, DueDate, ResolvedDate, StartDate, TimeSpentInSeconds, UpdatedByUser, UpdatedByPerformer, UpdatedForTechView, IsCurrentCategoryForTechsOnly, Username,… - **Create a Jitbit ticket** (Create). Create a new ticket in Jitbit. Returns the created ticket ID. Required: categoryId, body, subject, priorityId. - **Update a Jitbit ticket by ID** (Update). Update one or many ticket parameters in Jitbit by id. Returns an empty 204 response on success. Required: id. Subject and body are editable by admins or technicians only. - **Jitbit tickets add secondary assignee** (Add). Add a secondary assignee to a Jitbit ticket. Returns an empty 204 response on success. Required: ticket_id, user_id. - **Jitbit tickets close** (Close). Close a Jitbit ticket by id. Offers an option to close silently without sending email notifications. Returns 200 OK on success with no response body. Required: ticket_id. - **Jitbit tickets search** (Search). Search Jitbit tickets by text query with optional filters for creator, category, status, assignee, and date range. Returns: IssueID, Priority, StatusID, IssueDate, Subject, Status, UpdatedByUser, UpdatedByPerformer, CategoryID, UserName, Technician, FirstName, LastName, DueDate, TechFirstName, TechLastName, LastUpdated, UpdatedForTechView, UserID, CompanyID, CompanyName, AssignedToUserID,… - **Jitbit tickets merge** (Merge). Merge two Jitbit tickets together. The secondary ticket is merged into the primary ticket and the original secondary ticket is deleted. This action is irreversible. Returns 200 OK on success with no response body. Required: ticket_id, secondary_ticket_id. - **Jitbit tickets link** (Action). Link two Jitbit tickets together as related. Returns 200 OK on success with no response body. Required: ticket_id, other_ticket_id. - **Jitbit tickets unlink** (Action). Unlink two related Jitbit tickets. Returns 200 OK on success with no response body. Required: ticket_id, other_ticket_id. - **Jitbit tickets add subticket** (Add). Make one Jitbit ticket a subticket of another by linking a child ticket to a parent ticket. Returns an empty 204 response on success. Required: parent_ticket_id, child_ticket_id. - **Jitbit tickets remove subticket** (Delete). Remove a subticket relationship from a Jitbit ticket by child ticket ID. Returns an empty 204 response on success. Required: child_ticket_id. - **Jitbit tickets list linked** (List). List tickets linked as related to a given Jitbit ticket. Returns: TicketID, Subject, StatusID, UpdatedByUser, UpdatedByPerformer, CompanyID, UserID, Username, FirstName, LastName, IssueDate, Email, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id. - **Jitbit tickets list subtickets** (List). List first-level subtickets for a given Jitbit ticket. Returns: IssueID, Priority, StatusID, IssueDate, Subject, Status, UpdatedByUser, UpdatedByPerformer, CategoryID, UserName, Technician, FirstName, LastName, DueDate, TechFirstName, TechLastName, LastUpdated, UpdatedForTechView, UserID, CompanyID, CompanyName, AssignedToUserID, ResolvedDate, SectionID, Category, Origin, Email, HasChildren,… - **Jitbit tickets get parent** (Get). Get the parent ticket of a given Jitbit ticket. By default returns the parent ticket ID as plain text (zero if none found); with return_full_ticket set to true, returns the full ticket JSON including TicketID, Subject, Body, Status, Priority, IssueDate, CategoryID, AssignedToUserID, and Attachments. Required: ticket_id. - **Jitbit tickets add tag** (Add). Add a tag to a Jitbit helpdesk ticket. The tag can be new or existing. Returns 200 OK on success with no response body. Required: tag_name, ticket_id. - **List all Jitbit stats** (List). Get overall statistics for the Jitbit ticketing system, including counts of open, closed, new, unassigned, and unanswered tickets. Returns: TotalTickets, Closed, InProcess, NewTickets, Unanswered, Unassigned, Unclosed, HandledByMe, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech,… - **List all Jitbit priorities** (List). List all Jitbit ticket priorities, including standard and custom ones. Returns: PriorityID, Name, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. - **List all Jitbit companies** (List). List all companies in Jitbit. Returns: CompanyID, Name, EmailDomain, Notes, UserID, Username, Email, FirstName, LastName, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. - **Jitbit ticket custom fields set** (Set). Set a single custom field value on a Jitbit ticket. Returns an empty 200 response on success; an error message is returned otherwise. Required: ticket_id, field_id, value. For checkboxes pass true or false, for dropdowns pass the option ID, for dates pass a date string in any format. - **Jitbit ticket custom fields set many** (Set). Set multiple custom field values on a Jitbit ticket in one request. Returns 200 OK on success with no response body; an error message is returned otherwise. Required: ticket_id. Pass each custom field as a cf key (e.g., cf1624) with its value in the request body. - **List all Jitbit ticket custom fields** (List). List all custom fields and their values for a Jitbit ticket. Returns: FieldName, FieldID, Type, UsageType, Value, ValueWithOption, Mandatory, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id. - **List all Jitbit attachments** (List). List all file attachments for a Jitbit ticket. Returns: FileName, FileID, FileSize, IssueID, UserID, Url, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id. - **Create a Jitbit attachment** (Create). Attach a file to a Jitbit ticket via multipart form upload. Returns: FileName, FileID, FileSize, IssueID, UserID, Url, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id, uploadFile. - **Delete a Jitbit attachment by ID** (Delete). Delete a file attachment from a Jitbit ticket by file ID. Returns an empty 204 response on success. Required: id. - **Jitbit attachments download** (Download). Downloads a specific attachment file using the file's direct path, which is typically provided in the response of the message listing endpoint. The actual path must be replaced with the URI or download link of the attachment. - **Jitbit ticket subscribers add** (Add). Add a new subscriber to a Jitbit helpdesk ticket. Returns an empty 200 response on success. Required: ticket_id, user_id. - **Jitbit ticket subscribers remove** (Delete). Remove a subscriber from a Jitbit helpdesk ticket. Returns a 200 OK response on success with no response body. Required: ticket_id, user_id. - **List all Jitbit ticket subscribers** (List). List subscribers for a Jitbit helpdesk ticket. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: ticket_id. - **List all Jitbit categories** (List). List all Jitbit helpdesk categories the current user has permissions to see. Returns: CategoryID, Name, SectionID, Section, NameWithSection, ForTechsOnly, FromAddress, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. - **Jitbit categories list techs** (List). List all possible assignees (technicians) for a Jitbit helpdesk category. Returns: UserID, Username, FirstName, LastName, TicketsAssigned, FullNameAndLogin, FullName, Email, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: category_id. - **Create a Jitbit category** (Create). Create a new Jitbit helpdesk category. Returns the resulting category ID as a plain text integer with a 200 OK response. Required: name. - **List all Jitbit ticket templates** (List). Get the ticket template (pre-filled subject and body) for a category in JitBit. Returns: Subject, Body, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Returns null if no template is configured for the category. Required: category_id. - **List all Jitbit category custom fields** (List). List all custom fields available in a Jitbit ticket category, including dropdown options. Returns: FieldName, FieldID, Type, UsageType, ForTechsOnly, Mandatory, OrderByNumber, ShowInGrid, SelectionComboOptions, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager.… - **List all Jitbit ticket integration data** (List). Get all external integration data (Jira, GitHub, GitLab, Bitbucket, Asana, Trello, VSO, Harvest, Basecamp) linked to a Jitbit ticket. Returns: BitbucketIssueUrl, JiraIssueUrl, GitHubIssueUrl, AsanaTaskUrl, TrelloCardUrl, VSOWorkItemUrl, HarvestProjectUrl, GitLabIssueUrl, BasecampTodoUrl, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent,… - **List all Jitbit time spent** (List). List time spent log entries for a Jitbit ticket. Returns all individual time entries logged against the ticket. Returns: UserID, UserName, StatusID, TimeSpentInSeconds, Date, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id. - **Create a Jitbit time spent** (Create). Add a new time spent entry to a Jitbit ticket, logged under the current user. Returns 200 OK with 'ok' on success, or an error message on failure. Required: ticket_id, time_spent_in_seconds. - **Create a Jitbit comment** (Create). Post a comment to a Jitbit helpdesk ticket. Returns the created comment object including CommentID, IssueID, UserID, UserName, Email, Body, CommentDate, ForTechsOnly, IsSystem, and Recipients. Required: ticket_id, body. - **Update a Jitbit comment by ID** (Update). Update an existing Jitbit comment by id. The caller must be the comment author, a category tech, or an admin. Returns: CommentID, IssueID, UserID, UserName, Email, FirstName, LastName, IsSystem, CommentDate, ForTechsOnly, Body, TicketSubject, Recipients, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen,… - **List all Jitbit comments** (List). List comments for a Jitbit helpdesk ticket. Returns: CommentID, IssueID, UserID, UserName, Email, FirstName, LastName, IsSystem, CommentDate, ForTechsOnly, Body, TicketSubject, Recipients, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id. - **List all Jitbit comment templates** (List). List all available comment templates (canned responses) in Jitbit, optionally filtered by ticket category. Returns: TemplateId, Body, Name, CategoryIDs, GroupID, GroupName, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. - **List all Jitbit users** (List). List all Jitbit helpdesk users. Returns per record: UserID, Username, Email, FirstName, LastName, CompanyName, CompanyId, LastSeen, IsAdmin, Disabled, IsTech, IsManager. - **Get single Jitbit user by ID** (Get). Get a single Jitbit user by id. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: id. - **Jitbit users get by email** (Get). Get a single Jitbit user by email address. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: email. - **Jitbit users get by username** (Get). Get a single Jitbit user by username. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: username. - **Create a Jitbit user** (Create). Create a new Jitbit helpdesk user. Returns the newly created user's userId. Required: email. - **Update a Jitbit user by ID** (Update). Update a Jitbit user by id. All parameters except the user ID are optional. Returns an empty 200 response on success. Required: id. - **Delete a Jitbit user by ID** (Delete). Delete a Jitbit user by id. This action is irreversible. Returns an empty 200 response on success. Required: id. - **Jitbit users merge** (Merge). Merge two Jitbit users together, moving the from-user's data into the to-user. This action is irreversible. Returns an empty 200 response on success. Required: from_user_id, to_user_id. - **Jitbit user custom fields set** (Set). Set a custom field value for a Jitbit user. Pass the value as a string — for checkboxes pass true or false, for dropdowns pass the option ID, and for dates pass a date string in any format. Returns a 200 OK status on success or an error message on failure. Required: user_id, field_id, value. - **Jitbit user custom fields list custom fields** (List). List all custom fields configured for a Jitbit user. Returns an array of custom field objects including FieldName, FieldID, Type, and Value. Required: user_id. - **List all Jitbit assets** (List). Get a single Jitbit asset by id. Returns the full asset object including ItemID, ModelName, Manufacturer, Type, SerialNumber, Quantity, CompanyID, Tickets, AssignedUsers, and Fields. Required: id. - **Create a Jitbit asset** (Create). Create a new asset in Jitbit. Returns the created asset object including ItemID, ModelName, Manufacturer, Type, SerialNumber, Quantity, and CompanyID. Required: model_name. - **Update a Jitbit asset by ID** (Update). Update an existing asset in Jitbit by id. Returns the updated asset object including ItemID, ModelName, Manufacturer, Type, SerialNumber, Quantity, and CompanyID. Required: id, model_name. - **Jitbit assets assign to user** (Assign). Assign a Jitbit asset to a user. Returns a plain-text 200 OK on success or an error message otherwise. Required: asset_id, user_id. - **Jitbit assets unassign from user** (Action). Unassign a Jitbit asset from a user. Returns a plain-text 200 OK on success or an error message otherwise. Required: asset_id, user_id. - **Jitbit assets add to ticket** (Add). Add an asset to the 'assets involved' list of a Jitbit ticket. Returns an empty 200 response on success. Required: asset_id, ticket_id. - **Jitbit assets remove from ticket** (Delete). Remove a related asset from a Jitbit ticket. Returns an empty response on success. Required: asset_id, ticket_id. - **Jitbit assets enable** (Enable). Enable a JitBit asset by its asset ID, reactivating it in the helpdesk system. Returns an empty response on success. Required: asset_id. - **Jitbit assets disable** (Disable). Disable a JitBit asset by its asset ID, deactivating it in the helpdesk system. Returns an empty response on success. Required: asset_id. - **Jitbit asset custom fields set** (Set). Set a custom field value on a Jitbit asset. Returns 200 OK on success or an error message on failure. Required: asset_id, field_id, value. - **Create a Jitbit kb article** (Create). Create a new Knowledge Base article in Jitbit. Returns: ArticleId, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: category_id, body, subject, for_techs_only. - **Update a Jitbit kb article by ID** (Update). Update a Jitbit knowledge base article by id, modifying its category, body, subject, and technician-only visibility. Returns an empty 200 response on success. Required: id, category_id, body, subject.