Resources · Zapier integration

Metamint Helpdesk Zapier integrationAutomate Metamint Helpdesk with Zapier.

6 triggers, 6 actions, 0 searches. The Metamint Helpdesk Zapier integration watches tickets, replies and users in your WordPress support desk, and can create, answer, update or delete them for you. Here is how each piece works and what it costs.

Beta app Zapier still marks this integration as beta.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Metamint Helpdesk Zapier integration does

Metamint Helpdesk is a WordPress plugin that adds live chat, AI ticketing and a support dashboard to your site. Zapier links it to your other apps: a Zap (the automation you build on Zapier) reacts to tickets, replies and users, or writes them into the helpdesk from another tool.

Three outcomes show what it is for. A team heads-up: the Create Ticket trigger posts every new ticket in your team chat, so nobody has to keep the dashboard open. A log of closed tickets: the Update Ticket trigger fires on a status change and, behind a filter, writes the closed ones to a spreadsheet. Tickets from anywhere: the Create Ticket action opens a ticket from a form or an email tool, with a title and the customer's email.

Now the limits. All six triggers are polling: Zapier checks the helpdesk on a timer set by your plan, so nothing is instant. There is no search, so a Zap cannot look a ticket up by subject or customer; any Ticket ID has to come from an earlier step. Several triggers and actions share the same name, which is easy to mix up in the editor. And Zapier lists the app as beta.

Before you build, open our Zapier review. If you would rather hand the setup over, see our Zapier agency page.

Vocabulary

The Zapier words you will meet on this page

Eight terms, in plain English. They come back below without a reminder.

Zap
The automation itself: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap, such as a new ticket in Metamint Helpdesk. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something for you, like adding a reply.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant one is reported by the app the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
Connection
Your Metamint Helpdesk account linked to Zapier once, then reused by every Zap and step that needs it.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What it really costs

Checking Metamint Helpdesk for new tickets, replies or users never costs a task, however often Zapier looks. Only a completed action is billed.

  • Trigger checksFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

Each action that succeeds counts once: a Zap that adds one reply per new ticket costs one task per ticket. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps of two steps, so a trigger plus one action fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Metamint Helpdesk is not a premium app. All six triggers are polling, so the grid below sets the longest wait.

Connect

Connect Metamint Helpdesk to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Metamint Helpdesk account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Metamint Helpdesk

    Search for Metamint Helpdesk in the dialog, select it, then click Add connection. A new tab opens where you sign in on the helpdesk side to finish the link.

  3. 03

    Sign in and grant access

    Log in to Metamint Helpdesk in that tab and let Zapier reach the account. Every Zap that uses the helpdesk then reuses this one connection, so you sign in only once.

First Zap

Your first Zap: log every closed ticket

GoalWhen a ticket status changes in Metamint Helpdesk, a filter keeps the closed ones and each is written as a row in your spreadsheet.

  1. 01

    Set the trigger

    Create a Zap, choose Metamint Helpdesk and the Update Ticket trigger, the one that fires when a ticket status is updated, then select your connection.

  2. 02

    Test it

    Run the test: Zapier brings back the three most recent items of the connected account. Pick a ticket whose status really changed, so the filter has a real value to read.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Fill the three boxes: the status field, a text rule, and the value for closed as it appears at test.

  4. 04

    Add the action

    Pick your spreadsheet app and its add-row action, then map the ticket fields to your columns. Test the step and read what came back before going further.

  5. 05

    Publish

    Click Publish to switch the Zap on. With a filter it is a multi-step Zap, so it needs a paid plan. Tickets closed before publishing are not logged.

Triggers

Metamint Helpdesk triggers

6 events start a Zap when something happens in Metamint Helpdesk. Zapier checks for them at the interval your plan allows.

1

Add Reply

Polling trigger

In Zapier“Triggers when a new reply is added to a ticket.”

Despite its action-like name, this trigger starts your Zap each time a new reply is added to a ticket, and hands that reply to the next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to copy each reply into the record of the customer elsewhere, or to alert whoever owns the conversation.
Watch out
the editor also lists an Add Reply action; check you picked it under the trigger events, not the actions.
2

Create Ticket

Polling trigger

In Zapier“Triggers when a new ticket is created in Metamint Helpdesk.”

Picks up every new ticket created in Metamint Helpdesk and passes it to the next step, where you build the rest of the flow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to post new tickets in your team chat, or to send an acknowledgement with the Add Reply action.
Watch out
it shares its name with the Create Ticket action; as a trigger it watches tickets, it never opens one.
3

Update Ticket

Polling trigger

In Zapier“Triggers when a ticket status is updated.”

Fires when the status of a ticket is updated, which turns every move between open, in progress and closed into an event you can act on.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to log closed tickets, or to warn the person who owns a ticket when its status moves.
Watch out
it reacts to any status change, so add a filter on the status value if only one transition matters to you.
4

Delete Ticket

Polling trigger

In Zapier“Triggers when a ticket is permanently deleted.”

Starts the Zap when a ticket is permanently deleted, so the removal can be mirrored or recorded outside the helpdesk.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to keep an audit row of deleted tickets in a sheet, or to clean the matching entry in another tool.
Watch out
the ticket is gone from the helpdesk by then, so read at test which details the trigger still returns.
5

Create User

Polling trigger

In Zapier“Triggers when a new user is created.”

Reacts each time a new user is created, giving you one place to follow every account that appears on your support side.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to add each new user to your CRM, or to send a welcome message from your email tool.
Watch out
an action of the same name exists; pick this one under the trigger events when you want to watch, not create.
6

Delete User

Polling trigger

In Zapier“Triggers when a user is deleted.”

Fires when a user is deleted, so the systems around your helpdesk can follow suit instead of keeping a stale record.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to mark the contact as removed in your CRM, or to note the deletion in a shared sheet.
Watch out
users deleted before the Zap is published are never sent; only later deletions go through.
Actions

Metamint Helpdesk actions

Metamint Helpdesk gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Reply

Action

In Zapier“Adds a reply to an existing ticket.”

Posts a reply on an existing ticket, written by the Zap rather than by an agent.

When to use it
to send an acknowledgement on each new ticket, or to push an answer drafted in another app.
Watch out
Ticket ID and Message are required, and the ID must come from an earlier step since there is no search.
2

Create Ticket

Action

In Zapier“Creates a new support ticket in Metamint Helpdesk.”

Opens a new support ticket in the helpdesk from another app, so requests that arrive elsewhere join the same queue.

When to use it
when a form or an inbox outside WordPress receives support requests.
Watch out
Title and Customer Email are both required; map a column that is always filled for each.
3

Create User

Action

In Zapier“Creates a new user in WordPress.”

Creates a new user in WordPress, the site the helpdesk runs on, from details held in another tool.

When to use it
when a sign-up handled elsewhere should give someone an account on your site.
Watch out
Email is the only required field; check at test what else the action offers to fill.
4

Delete Ticket

Action

In Zapier“Permanently deletes a support ticket.”

Removes a support ticket for good, without anyone opening the dashboard.

When to use it
for clean-up flows, when another tool decides that a ticket should go.
Watch out
the deletion is permanent and Ticket ID is required; map it from an earlier step and check at test which ID arrives.
5

Delete User

Action

In Zapier“Deletes a user from WordPress.”

Deletes a user from WordPress, the site behind the helpdesk, when another tool says the account should go.

When to use it
to keep your site in step when someone is removed from your main customer list.
Watch out
User ID is required and comes from an earlier step; check at test which ID arrives before publishing.
6

Update Ticket

Action

In Zapier“Updates a ticket status (open, in-progress, closed).”

Changes the status of a ticket to open, in progress or closed, from outside the dashboard.

When to use it
when work tracked in another tool should move the ticket along, for example closing it once a task is done there.
Watch out
Ticket ID and Status are both required; read the accepted values at test.
When it breaks

When it breaks

Zapier lists no error specific to Metamint Helpdesk, which it still marks as beta. What goes wrong comes from how Zapier works.

  • Older tickets never arrive

    A Zap only reacts to what happens after it is switched on. Existing tickets, replies and users are not picked up; moving that backlog is a separate job.

  • A Zap that keeps restarting itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again and burn through tasks.

  • A big batch gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.

  • The same ticket does not fire twice

    On a polling trigger, Zapier remembers what it has already seen, so one ticket or reply never starts the same Zap twice.
Need help

Need help automating Metamint Helpdesk with Zapier?

A person reads every message.

FAQ

Metamint Helpdesk and Zapier: frequent questions

01Is the Metamint Helpdesk Zapier integration free?
Yes, within the two-step limit. Metamint Helpdesk is not a premium app, so it runs on Zapier's free plan, which gives 100 tasks a month and unlimited Zaps of two steps: one trigger and one action. Posting each new ticket in your team chat fits that frame. As soon as you add a filter, for instance to keep only closed tickets, or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Metamint Helpdesk Zap use?
One task per action that succeeds. Zapier checking the helpdesk for tickets, replies or users costs nothing, however often it looks. A Zap that adds an acknowledgement reply to each new ticket costs one task per ticket; if it also posts in your team chat, two. A failed action is not counted, and a filter that stops the Zap means the actions after it never run. A few apps and actions take more than one task when they complete.
03Do Metamint Helpdesk tickets reach Zapier in real time?
No. All six Metamint Helpdesk triggers are polling: Zapier asks the helpdesk for new items at a fixed interval. On the free plan that is every 15 minutes, on Professional every 2 minutes, on Team and Enterprise every minute. On the paid plans the interval can be changed, and a check can be run by hand from the editor. A ticket opened just after a check waits for the next one, so plan your response times around it.
04What do you need to connect Metamint Helpdesk to Zapier?
An account on Metamint Helpdesk, plus read or write access on anything you do not own yourself and want the Zap to touch. You connect it once from the Apps page of your Zapier account: click + Add connection, search for Metamint Helpdesk, click Add connection, sign in in the tab that opens and grant access. Every Zap that uses the helpdesk, triggers and actions alike, then reuses that connection, with nothing to redo.
05Why do the triggers and actions have the same names?
Because the app labels them that way. Add Reply, Create Ticket, Update Ticket, Delete Ticket, Create User and Delete User each exist twice: once as a trigger that watches the event, once as an action that does it. The trigger called Update Ticket fires on a status change; the action called Update Ticket sets a status. In the editor, check whether you are choosing a trigger event or an action event before you pick a label.
06What if the Metamint Helpdesk operation you need is missing?
Then Zapier cannot do it for Metamint Helpdesk today. The app currently offers six triggers and six actions, with no search, so a Zap cannot look up a ticket by subject or customer; every Ticket ID or User ID must come from an earlier step. The Metamint Helpdesk page on Zapier shows the current list of operations, worth checking before you plan. Within that frame, start from a ticket trigger and check at test that it carries the ID your action needs.
07Zapier, Make or n8n for Metamint Helpdesk?
Judge on criteria rather than a ranking. On Zapier, every Metamint Helpdesk trigger is polling, so your plan sets the delay, from every 15 minutes on the free plan down to every minute on Team and Enterprise. Flows that sort tickets need a filter and therefore a paid plan, and each successful action is billed. Whether Make or n8n carry a Metamint Helpdesk connector is not covered here: check their catalogues, then compare delay and billing for the same flow.
Same platform

Other docs you might need on this stack.

Browse all integrations