Integration
Connect Jitbit Helpdesk to Mercury
When New Ticket fires in Jitbit Helpdesk, your agent runs Add customer in Mercury. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Jitbit Helpdesk and Mercury to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Jitbit Helpdesk can start in Mercury
When New Ticket in Jitbit Helpdesk
then Add customer in Mercury
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 Mercury
Triggers and actions 1 trigger · 36 actions
- New Ticket
Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.
- Add article
Creates a new knowledge base article in a category.
- Add asset
Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.
- Add company
Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.
- Add tag to ticket
Adds a tag to a ticket. The tag is created if it does not already exist.
- Add time spent
Logs a time spent entry on a ticket under the connected user. Requires technician permissions.
- Create New Reply
Posts a new reply (comment) to an existing helpdesk ticket.
- Create Ticket
Creates a new helpdesk ticket in a category, with a subject, body and priority.
- Create User
Creates a new helpdesk user. Requires administrator permissions.
- Find Ticket
Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.
- Find User
Finds a helpdesk user by their email address and returns their profile.
- Get Article
Returns a knowledge base article with its full content, category, tags and attachments.
- Get ticket
Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.
- List Companies
Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.
- List Ticket Comments
Returns all comments (replies) posted on a Jitbit Helpdesk ticket.
- List tickets
Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.
- 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.
- Update company
Updates a company's name, notes and email domains in Jitbit Helpdesk.
- 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.
- Update user
Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.
- Add customer
Creates a new Accounts Receivable customer in Mercury that you can invoice.
- Add internal transfer
Transfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
- Add recipient
Creates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
- Get invoice
Returns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
- Get organization
Returns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
- Get recipient
Returns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
- Get transaction
Returns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
- List accounts
Returns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
- List account statements
Returns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
- List categories
Returns the organization's custom expense categories used to classify transactions.
- List customers
Returns the accounts receivable customers on your Mercury account (up to 1000).
- List invoices
Returns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
- List recipients
Returns the payment recipients saved in your Mercury account (up to 1000).
- List transactions
Returns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
- Send money
Sends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
- Update recipient
Updates an existing payment recipient's name, contact details and payment routing information.
- Update transaction
Updates the note and/or category of an existing Mercury transaction.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Jitbit Helpdesk
Jitbit Helpdesk to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Jitbit Helpdesk to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Jitbit Helpdesk to MailchimpMailchimp marketing automation and email platform.
Jitbit Helpdesk to StripeStripe is a payment processing platform for online businesses.
Jitbit Helpdesk to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Jitbit Helpdesk to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Mercury
HubSpot to MercuryHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to MercuryGoogle Sheets
Gmail to MercuryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MercuryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Jitbit Helpdesk and Mercury, 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 Mercury when something happens in Jitbit Helpdesk?
Any of Mercury's 17 actions, including Send money, Update recipient, Update transaction and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mercury to Jitbit Helpdesk?
Mercury has no triggers in the catalog today, so automations start in Jitbit Helpdesk. If you need the other direction, ask: your agent reads Mercury's API documentation and adds it.
Do I have to build a connector for Jitbit Helpdesk or Mercury?
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 Mercury 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.