Mojo Helpdesk Zapier integrationAutomate Mojo Helpdesk with Zapier.
The Mojo Helpdesk Zapier integration gives you 4 triggers, 2 actions and 0 searches. The triggers watch new unassigned tickets and new users on a timer, and the actions create a ticket or a user. It works on the free plan. Here is what each does and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mojo Helpdesk Zapier integration actually does
Mojo Helpdesk is help desk software that gathers customer requests and internal tickets in one place, then lets you assign and follow them. The Zapier integration links it to your other tools: new tickets and users leave the help desk, and requests from elsewhere become tickets.
No ticket left waiting in silence. New Ticket reacts to unassigned tickets, the ones nobody has picked up yet. Send each one to your team chat and someone claims it without refreshing the queue.
Tickets from every channel. Create Ticket turns a web form entry, a bug report or a sales request from another tool into a ticket in the queue you choose, with its title and description filled in.
Accounts created for you. Create User adds a person to Mojo Helpdesk from your signup form or another app, and can send them the welcome email if you tick that option.
Now the limits. The four triggers only see new tickets that are unassigned, so a ticket created already assigned to an agent does not start a Zap. There is no trigger for a ticket that changes status or gets a reply, no action to update or close a ticket, and no search step to find an existing one. Every trigger is polling, so each reaction waits for Zapier's next check.
If you are deciding which automation tool to use, see our n8n vs Zapier comparison.
Zapier vocabulary in one minute
Seven terms carry this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it on your behalf.
- Action
- What the Zap does once it starts: the step that writes, sends or moves something for you, in Mojo Helpdesk or elsewhere.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's quota is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the new ones. All four here are polling.
- Instant trigger
- A trigger the app reports itself, so nothing waits for a check. Mojo Helpdesk has none of these on Zapier.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it otherwise.
What a Mojo Helpdesk Zap costs
Zapier bills tasks, and only actions that succeed count. Watching your help desk for new tickets is free, however often Zapier checks.
- Trigger checkFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, Zaps of 2 steps
- Premium appNo, works on the free plan
A Zap that posts each new unassigned ticket to your team chat uses one task per ticket; add a second action and each ticket costs two. Failed actions are not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A filter or a second action makes it a multi-step Zap (anything beyond one trigger and one action), which needs a paid plan. Mojo Helpdesk is not a premium app. The grid below shows how often Zapier checks the four polling triggers on each plan.
Connect your Mojo Helpdesk account to Zapier
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your Mojo Helpdesk account linked to Zapier once, then reused by every step that uses it.
- 02
Pick Mojo Helpdesk
Search for Mojo Helpdesk in the dialog, select it in the results, then click Add connection. A new browser tab opens where you sign in to your help desk account.
- 03
Sign in and grant access
Log in to Mojo Helpdesk in that tab and let Zapier reach the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: unassigned tickets in your team chat
GoalEach new unassigned ticket in Mojo Helpdesk is posted to your team chat, but only when it matches a condition you set.
- 01
Create the Zap
Start a new Zap, choose Mojo Helpdesk as the app that starts it and New Ticket as the event, then select your Mojo Helpdesk connection.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent tickets of the connected account, so you build the message on a real one.
- 03
Add the filter
Add a Filter step from the plus icon and set the field, the rule and the value. A filter makes this a multi-step Zap, which needs a paid plan.
- 04
Add the chat message
Choose your team chat as the action and map the ticket's title and description into the message. Test the step once and read what came back.
- 05
Publish
Publish the Zap to switch it on. Zapier now checks Mojo Helpdesk at your plan's interval and posts each new ticket that passes.
Mojo Helpdesk triggers on Zapier
4 events start a Zap when something happens in Mojo Helpdesk. Zapier checks for them at the interval your plan allows.
New Ticket
Polling triggerIn Zapier“Triggers when new unassigned ticket is created.”
Starts a Zap for every new ticket that nobody has been assigned to yet. It is the natural trigger for making sure a fresh request gets an owner.
New Ticket With Due On
Polling triggerIn Zapier“Triggers when new unassigned ticket with a due on date is created.”
Fires for new unassigned tickets that carry a due date. A deadline marks a ticket that needs watching, and this trigger lets you handle those apart from the rest.
New Ticket With Scheduled On
Polling triggerIn Zapier“Triggers when new unassigned ticket with a scheduled on date is created.”
Reacts to new unassigned tickets that have a scheduled date. It suits work that is planned ahead rather than handled on arrival.
New User
Polling triggerIn Zapier“Triggers when new user is created.”
Fires each time a user is created in Mojo Helpdesk. Useful to keep your other tools aware of who can now open or handle tickets.
Mojo Helpdesk actions on Zapier
Mojo Helpdesk gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Ticket
ActionIn Zapier“Create new ticket.”
Opens a new ticket in Mojo Helpdesk with data from an earlier step, placed in the queue you pick.
Create User
ActionIn Zapier“Create new user.”
Adds a new user to Mojo Helpdesk from details another app provides, such as an email address and a first name.
When a Mojo Helpdesk Zap breaks
Zapier links no help article and no app-specific limit to Mojo Helpdesk. What goes wrong comes from Zapier's general behavior, and it applies here too.
Four cases worth knowing before you switch anything on. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.
Old tickets are never picked up
A Zap only reacts to what happens after it is switched on. Tickets and users already in Mojo Helpdesk stay put; moving that backlog is a separate job.A Zap can set itself off again
A Zap that writes into the very place its own trigger watches can start itself over and over, and burn through your task count fast.A bulk import can be held back
When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back.The same ticket will not run twice
On a polling trigger, Zapier remembers what it has already seen, so the same ticket or user does not start the Zap a second time.
Need help automating Mojo Helpdesk with Zapier?
A person reads every message.
