Integration
Connect Mojo Helpdesk to Ashby
When New Ticket fires in Mojo Helpdesk, your agent runs Create Candidate Note in Ashby. 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 Mojo Helpdesk and Ashby 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Mojo Helpdesk can start in Ashby
When New Ticket in Mojo Helpdesk
then Create Candidate Note in Ashby
When New Ticket With Due On in Mojo Helpdesk
then Add candidate tag in Ashby
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 Mojo Helpdesk and Ashby
Triggers and actions 4 triggers · 40 actions
Trigger
New TicketTriggers when a new ticket is created in Mojo Helpdesk.
Trigger
New Ticket With Due OnTriggers when a new Mojo Helpdesk ticket that has a due date is created.
Trigger
New Ticket With Scheduled OnTriggers when a new Mojo Helpdesk ticket that has a scheduled date is created.
Trigger
New UserTriggers when a new user is created in Mojo Helpdesk.
Action
Add assetCreates a new asset in Mojo Helpdesk Asset Management and returns the created asset.
Action
Add Comment to TicketAdds a public comment to a Mojo Helpdesk ticket.
Action
Add Staff Note to TicketAdds an internal staff-only note to a Mojo Helpdesk ticket.
Action
Add Tag to TicketAdds a tag to a Mojo Helpdesk ticket, creating the tag if it does not exist.
Action
Add task to ticketCreates a task on a ticket, with optional notes, due date, assignee and completion status.
Action
Create TicketCreates a new ticket in Mojo Helpdesk and returns it.
Action
Create UserCreates a new user in Mojo Helpdesk.
Action
Delete ticketPermanently deletes a ticket, including its comments and attachments.
Action
Delete userPermanently deletes a user from Mojo Helpdesk. This cannot be undone.
Action
Find assets by criteriaReturns the assets that match a search query, such as a name, tag, serial number, location or assigned user.
Action
Find User by EmailFinds a Mojo Helpdesk user by email address.
Action
Get assetReturns the details of a single asset, including its status, location, assigned users and attached files.
Action
Get TicketReturns one Mojo Helpdesk ticket by its ID, including title, description, status, priority and assignee.
Action
Get UserReturns one Mojo Helpdesk user by ID.
Action
List commentsReturns the comments on a Mojo Helpdesk ticket, including staff notes.
Action
List ticket queuesReturns the ticket queues in your Mojo Helpdesk account, with each queue's id, name and email settings.
Action
List ticketsReturns the tickets in your Mojo Helpdesk, sorted by the field and order you choose.
Action
List usersReturns the users (end users and agents) in your Mojo Helpdesk account.
Action
Remove tag from ticketRemoves a tag from a ticket, identified by the tag's ID or label, and returns the ticket's remaining tags.
Action
Search TicketsFinds Mojo Helpdesk tickets matching a search query (same syntax as the web app's advanced search).
Action
Update assetUpdates an existing asset in Mojo Helpdesk, changing only the fields you supply.
Action
Update TicketUpdates an existing Mojo Helpdesk ticket; only the fields you supply change.
Action
Update UserUpdates a Mojo Helpdesk user's details; only the fields you supply change (email cannot be changed here).
Action
Add candidate tagAdds an existing tag to a candidate in Ashby and returns the updated candidate.
Action
Add jobCreates a new job in Ashby with a title, department/team and location, optionally applying a job template, interview plan, employment type and brand.
Action
Add offerCreates an offer for a candidate's application in Ashby by submitting the offer form for an offer process that has already been started.
Action
Change Job Consideration StageMoves a candidate's application (their consideration for a job) to a different interview stage, optionally with an archive reason and rejection email when archiving.
Action
Consider Candidate for JobConsiders a candidate for a job in Ashby by creating a new application, optionally placing it in a specific interview plan and stage with a source and credited user.
Action
Create CandidateCreates a new candidate in Ashby with their name, contact details, social profiles, location and source.
Action
Create Candidate NoteAdds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.
Action
Find CandidateReturns up to 100 candidates whose email address and/or name match the values you supply.
Action
Find JobReturns up to 100 jobs whose title or requisition ID matches the text you search for.
Action
Find Job ConsiderationReturns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.
Action
Find OpeningReturns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.
Action
Get candidateReturns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.
Action
List departmentsReturns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.
Action
List locationsReturns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.
Action
Update CandidateUpdates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.
Action
Update jobUpdates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.
Action
Update OpeningUpdates an existing opening in Ashby, such as its identifier, description, department, target dates, backfill flag or employment type. Returns the updated opening.
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 Mojo Helpdesk
Mojo Helpdesk to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mojo Helpdesk to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mojo Helpdesk to StripeStripe is a payment processing platform for online businesses.
Mojo Helpdesk to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mojo Helpdesk to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Mojo Helpdesk to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Ashby
HubSpot to AshbyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to AshbySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to AshbySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AshbyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AshbyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AshbyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Mojo Helpdesk and Ashby, answered
What can start an automation from Mojo Helpdesk?
Any of Mojo Helpdesk's 4 triggers in the catalog, including New Ticket, New Ticket With Due On, New Ticket With Scheduled On and New User. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ashby when something happens in Mojo Helpdesk?
Any of Ashby's 17 actions, including Create Candidate, Create Candidate Note, Update Candidate and Update job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ashby to Mojo Helpdesk?
Ashby has no triggers in the catalog today, so automations start in Mojo Helpdesk. If you need the other direction, ask: your agent reads Ashby's API documentation and adds it.
Do I have to build a connector for Mojo Helpdesk or Ashby?
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 Mojo Helpdesk and Ashby 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.