--- title: "Connect Jitbit Helpdesk to Hamsa - APIANT.ai" description: "When \"New Ticket\" fires in Jitbit Helpdesk, your agent runs \"Add knowledge base item\" in Hamsa." canonical: "https://apiant.ai/connect/jitbit-helpdesk-to-hamsa" --- # Connect Jitbit Helpdesk to Hamsa When **New Ticket** fires in [Jitbit Helpdesk](https://apiant.ai/connections/jitbit-helpdesk), your agent runs **Add knowledge base item** in [Hamsa](https://apiant.ai/connections/hamsa). Describe the whole flow and it is built, tested on every scenario and kept running. Jitbit Helpdesk **1** trigger Jitbit Helpdesk **19** actions Hamsa **21** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Jitbit Helpdesk and Hamsa to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Jitbit Helpdesk can start in Hamsa - When **New Ticket** in Jitbit Helpdesk then **Add knowledge base item** in Hamsa - When **New Ticket** in Jitbit Helpdesk then **Add phone number** in Hamsa Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Jitbit Helpdesk and Hamsa ## Triggers and actions 1 trigger · 40 actions - Trigger **New Ticket** Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag. - Action **Add article** Creates a new knowledge base article in a category. - Action **Add asset** Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier. - Action **Add company** Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken. - Action **Add tag to ticket** Adds a tag to a ticket. The tag is created if it does not already exist. - Action **Add time spent** Logs a time spent entry on a ticket under the connected user. Requires technician permissions. - Action **Create New Reply** Posts a new reply (comment) to an existing helpdesk ticket. - Action **Create Ticket** Creates a new helpdesk ticket in a category, with a subject, body and priority. - Action **Create User** Creates a new helpdesk user. Requires administrator permissions. - Action **Find Ticket** Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets. - Action **Find User** Finds a helpdesk user by their email address and returns their profile. - Action **Get Article** Returns a knowledge base article with its full content, category, tags and attachments. - Action **Get ticket** Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values. - Action **List Companies** Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account. - Action **List Ticket Comments** Returns all comments (replies) posted on a Jitbit Helpdesk ticket. - Action **List tickets** Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates. - Action **List Time Spent Entries** Returns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions. - Action **Update company** Updates a company's name, notes and email domains in Jitbit Helpdesk. - Action **Update ticket** Updates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body. - Action **Update user** Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions. - Action **Add knowledge base item** Create a new knowledge base item for a voice agent. - Action **Add phone number** Add a phone number for a user. - Action **Add transcription job** Create a new asynchronous job (e.g. transcription). - Action **Add TTS voice** Create a new text-to-speech voice. - Action **Add voice agent** Create a new AI voice agent. - Action **Assign phone number** Assign a phone number to a voice agent. - Action **Delete knowledge base item** Delete a knowledge base item by ID. - Action **Delete phone number** Delete a phone number. - Action **Delete TTS voice** Delete a text-to-speech voice by ID. - Action **Get campaign** Get a campaign by ID. - Action **Get conversation** Get a call conversation record by ID. - Action **Get job** Get a single job's details by ID. - Action **Get voice agent** Retrieve a specific voice agent by ID. - Action **Initiate voice agent call** Initiate an outbound call with a voice agent via Twilio. - Action **List jobs** List jobs. - Action **List knowledge base items** Return a list of knowledge base items. - Action **List phone numbers** Return a list of phone numbers for a user. - Action **List TTS voices** Retrieve the list of available TTS voices. - Action **List voice agents** Retrieve a list of the account's voice agents. - Action **Transcribe audio** Generate a speech-to-text transcription from audio (not streamed). - Action **Update voice agent** Update an existing voice agent's configuration. ## Each app on its own - [ **Jitbit Helpdesk** A great help desk app for small and medium sized companies.](https://apiant.ai/connections/jitbit-helpdesk) - [ **Hamsa** AI voice agent platform with lifelike avatars, RAG-powered conversations, and API/SDK for calls, CRM, and...](https://apiant.ai/connections/hamsa) Reviews ## What our customers say ## More from Jitbit Helpdesk - [ **Jitbit Helpdesk to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/jitbit-helpdesk-to-salesforce) - [ **Jitbit Helpdesk to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/jitbit-helpdesk-to-slack) - [ **Jitbit Helpdesk to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/jitbit-helpdesk-to-mailchimp) - [ **Jitbit Helpdesk to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/jitbit-helpdesk-to-stripe) - [ **Jitbit Helpdesk to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/jitbit-helpdesk-to-shopify) - [ **Jitbit Helpdesk to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/jitbit-helpdesk-to-quickbooks-online) ## More into Hamsa - [ **MySQL to Hamsa** Connect directly to a MySQL database and run SQL statements from your automations.](https://apiant.ai/connect/mysql-to-hamsa) - [ **TimelinesAI to Hamsa** TimelinesAI allows you to share access to your personal or business Whatsapp account, integrate it with...](https://apiant.ai/connect/timelinesai-to-hamsa) - [ **HubSpot to Hamsa** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-hamsa) - [ **Salesforce to Hamsa** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-hamsa) - [ **Slack to Hamsa** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-hamsa) - [ **Google Sheets to Hamsa** Google Sheets](https://apiant.ai/connect/google-sheets-to-hamsa) Questions ## Jitbit Helpdesk and Hamsa, answered ### ### What can start an automation from Jitbit Helpdesk? Any of Jitbit Helpdesk's 1 trigger in the catalog, including New Ticket. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Hamsa when something happens in Jitbit Helpdesk? Any of Hamsa's 21 actions, including Update voice agent, Add knowledge base item, Add phone number and Add transcription job. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Hamsa to Jitbit Helpdesk? Hamsa has no triggers in the catalog today, so automations start in Jitbit Helpdesk. If you need the other direction, ask: your agent reads Hamsa's API documentation and adds it. ### ### Do I have to build a connector for Jitbit Helpdesk or Hamsa? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Jitbit Helpdesk and Hamsa without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.