Integration
Connect Homebase360 and Mojo Helpdesk
When New Customer fires in Homebase360, your agent runs Add Comment to Ticket in Mojo Helpdesk, or New Ticket in Mojo Helpdesk to Add task in Homebase360. 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 Homebase360 and Mojo Helpdesk 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 Homebase360 and Mojo Helpdesk can do together
From Homebase360 to Mojo Helpdesk
When New Customer in Homebase360
then Add Comment to Ticket in Mojo Helpdesk
When New Estimate in Homebase360
then Add Staff Note to Ticket in Mojo Helpdesk
From Mojo Helpdesk to Homebase360
When New Ticket in Mojo Helpdesk
then Add task in Homebase360
When New Ticket With Due On in Mojo Helpdesk
then Create Customer in Homebase360
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 Homebase360 and Mojo Helpdesk
Triggers and actions 11 triggers · 42 actions
Trigger
New CustomerTriggers when a new customer is added in Homebase360.
Trigger
New EstimateTriggers when a new estimate is created in Homebase360.
Trigger
New JobTriggers when a new job is created in Homebase360.
Trigger
New LeadTriggers when a new lead is created in Homebase360.
Trigger
Updated CustomerTriggers when a Homebase360 customer is added or changed.
Trigger
Updated EstimateTriggers when a Homebase360 estimate is created or changed, including sent, approved, declined or converted.
Trigger
Updated JobTriggers when a Homebase360 job is created or changed, including status, payment and schedule updates.
Action
Add estimateCreates a draft estimate (quote) in Homebase360 for an existing customer or for new contact details, which are matched to or saved as a customer. The estimate is not sent.
Action
Add taskCreates a task (to-do or reminder) in Homebase360, optionally attached to a customer and assigned to employees.
Action
Create CustomerCreates a Homebase360 customer with contact details, notes and tags.
Action
Create JobCreates a scheduled Homebase360 job for an existing customer with one line item.
Action
Create LeadCreates a Homebase360 lead for an existing customer, or finds or creates the customer from the details given.
Action
Get CustomersReturns Homebase360 customers matching a customer ID, phone, email or name.
Action
Get JobsReturns Homebase360 jobs by job ID, customer or date range.
Action
Get LeadsReturns Homebase360 leads by lead ID, customer or stage.
Action
List employeesReturns your Homebase360 team members, optionally filtered by employee ID, exact email, or a name/email search.
Action
List estimatesReturns estimates (quotes), optionally filtered by customer, a single estimate, or a created-date range.
Action
List invoicesReturns invoices from Homebase360 with totals, paid and outstanding amounts, status, payment types and line items, optionally filtered by customer, type, status or date range.
Action
List tasksReturns tasks (to-dos and reminders), optionally filtered by customer, employee, status or date range.
Action
Send estimateSends an existing estimate to its customer as a PDF by email and/or a link by text message.
Action
Send messageSends an SMS or MMS text message to an existing Homebase360 customer by mobile phone or customer ID.
Action
Update CustomerUpdates an existing Homebase360 customer; only the fields you provide change.
Action
Update estimateUpdates an existing estimate's line items, discount, note, lead source or salesperson in Homebase360.
Action
Update jobUpdates an existing job's schedule, note, assigned employees, line items or lead source in Homebase360.
Action
Update leadUpdates an existing lead's pipeline, stage, note, lead source, assignees or line items.
Action
Update taskUpdates an existing Homebase360 task — status, title, schedule, assignees, reminder or a new note.
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).
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 Homebase360
Homebase360 to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Homebase360 to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Homebase360 to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Homebase360 to MailchimpMailchimp marketing automation and email platform.
Homebase360 to StripeStripe is a payment processing platform for online businesses.
Homebase360 to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Mojo Helpdesk
HubSpot to Mojo HelpdeskHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Mojo HelpdeskGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Mojo HelpdeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Mojo HelpdeskGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Mojo HelpdeskGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Mojo HelpdeskMailchimp marketing automation and email platform.
Questions
Homebase360 and Mojo Helpdesk, answered
What can start an automation from Homebase360?
Any of Homebase360's 7 triggers in the catalog, including New Customer, New Estimate, New Job and New Lead. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mojo Helpdesk when something happens in Homebase360?
Any of Mojo Helpdesk's 23 actions, including Create Ticket, Create User, Update asset and Update Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mojo Helpdesk to Homebase360?
Yes. When something happens in Mojo Helpdesk, your agent can act in Homebase360 too. This page covers both directions: Mojo Helpdesk's triggers and Homebase360's actions are listed here as well.
Do I have to build a connector for Homebase360 or Mojo Helpdesk?
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 Homebase360 and Mojo Helpdesk 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.