# Connect Jitbit Helpdesk and Reply When **New Ticket** fires in [Jitbit Helpdesk](https://apiant.ai/connections/jitbit-helpdesk), your agent runs **Add contact list** in [Reply](https://apiant.ai/connections/reply), or **New Email Opened** in Reply to **Add tag to ticket** in Jitbit Helpdesk. Describe the whole flow and it is built, tested on every scenario and kept running. Jitbit Helpdesk **1** trigger Jitbit Helpdesk **19** actions Reply **7** triggers Reply **16** 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 Reply to do together? Give your AI client this address. `https://mcp.apiant.ai` 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 and Reply can do together ### From Jitbit Helpdesk to Reply - When **New Ticket** in Jitbit Helpdesk then **Add contact list** in Reply - When **New Ticket** in Jitbit Helpdesk then **Add note to contact** in Reply ### From Reply to Jitbit Helpdesk - When **New Email Opened** in Reply then **Add tag to ticket** in Jitbit Helpdesk - When **New Emails Sent** in Reply then **Create Ticket** in Jitbit Helpdesk 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 Reply ## Triggers and actions 8 triggers · 35 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. - Trigger **Inbox Category Set for Reply** Triggers when an email reply in Reply is given an inbox category, automatically or by a user. - Trigger **New Email Opened** Triggers when a contact opens a tracked email sent from Reply. - Trigger **New Emails Sent** Triggers when Reply sends an email from a sequence step. - Trigger **New Link Clicked** Triggers when a recipient clicks a tracked link in an email sent from Reply. - Trigger **New Person Bounce** Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server. - Trigger **New Person Opt Out** Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact). - Trigger **Prospect Finished** Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually. - Action **Add contact list** Creates a new contact list in Reply, optionally shared with your team. - Action **Add note to contact** Adds a note to a contact's timeline in Reply. - Action **Add sequence** Creates a new sequence in Reply with its steps, schedule, sending accounts and settings. - Action **Create\Update Person** Creates a Reply contact, or updates the existing contact with the same email address. - Action **Delete contact** Deletes a contact from your Reply account. - Action **Find contacts by criteria** Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step. - Action **Get contact** Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields. - Action **Get sequence** Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps. - Action **List contact lists** Returns the contact lists you own plus those shared with your team, optionally filtered by name. - Action **List contacts** Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL. - Action **List inbox categories** Returns the inbox categories you can file conversations under. - Action **List Sequence Contacts** Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status. - Action **List sequences** Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name. - Action **Mark as Finished** Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps. - Action **Remove Person From Campaign** Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account. - Action **Send Test Webhook Event** Sends a test event from an existing Reply webhook subscription to its configured URL. ## Each app on its own - [ **Jitbit Helpdesk** A great help desk app for small and medium sized companies.](https://apiant.ai/connections/jitbit-helpdesk) - [ **Reply** Reply is a sales automation platform that puts outreach on autopilot, while still making each communication...](https://apiant.ai/connections/reply) 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 Reply - [ **HubSpot to Reply** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-reply) - [ **Google Sheets to Reply** Google Sheets](https://apiant.ai/connect/google-sheets-to-reply) - [ **Gmail to Reply** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-reply) - [ **Google Calendar to Reply** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-reply) - [ **Google Drive to Reply** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-reply) - [ **Mailchimp to Reply** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-reply) Questions ## Jitbit Helpdesk and Reply, 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 Reply when something happens in Jitbit Helpdesk? Any of Reply's 16 actions, including Create\Update Person, Send Test Webhook Event, Add contact list and Add note to contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Reply to Jitbit Helpdesk? Yes. When something happens in Reply, your agent can act in Jitbit Helpdesk too. This page covers both directions: Reply's triggers and Jitbit Helpdesk's actions are listed here as well. ### ### Do I have to build a connector for Jitbit Helpdesk or Reply? 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. ### ### 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.