Resources · Make integration

IPEX Helpdesk Make integrationAutomate IPEX Helpdesk with Make.

Can Make run the repetitive side of your support desk? The IPEX Helpdesk Make integration gives you 32 modules, 28 actions and 4 searches, with no trigger. This guide is for support leads: connect the account, build a first scenario, then pick the right module.

Try the IPEX Helpdesk integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the IPEX Helpdesk Make integration let you automate?

The IPEX Helpdesk Make integration links your helpdesk account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick. Here it is either an action that creates or updates a ticket, a customer or a user account, or a search that finds them. IPEX Helpdesk has no trigger, so another app or the Make schedule starts the scenario.

Tickets from outside channels. A form or chat tool starts the scenario, Create a Ticket opens the request and Add a Ticket Tag files it for the right queue. Visitors without an account go through Create an Anonymous Ticket instead.

A customer base without duplicates. When a deal closes in your CRM, Search Customers checks whether the company is already there, Create a Customer adds it if not, and Add a User into Customer attaches the contact to it.

Reports on support work. Search Tickets pulls the tickets of an account and Get Track Time Records returns the time logged on them, ready to send to a spreadsheet app.

Know the limit before you start: Make marks its own documentation for IPEX Helpdesk as limited, with no official description per module and no connection guide. The notes below read each module from its name, so test it with Run once and read what comes back. The Make review explains how the editor works, and Make troubleshooting helps when a run fails.

Many apps also have an n8n node. If you are weighing the two tools, n8n vs Make sets out the criteria.

Connect

How do you connect IPEX Helpdesk to Make?

  1. 01

    Add an IPEX Helpdesk module

    In your scenario, click the +, type IPEX Helpdesk and pick any of its modules. The module opens with an empty connection field. Click Create a connection: a connection is your helpdesk account linked to Make, set up once and reused by every module of the app.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, yet a clear label such as IPEX support desk pays off when you manage several accounts or hand a scenario to a colleague.

  3. 03

    Authorize Make and save

    Depending on what the window shows, sign in to IPEX Helpdesk to authorize Make, or paste the key IPEX Helpdesk gives you. Click Save. Back in the module, the new connection is selected and you can fill in the fields.

First scenario

Build your first scenario with IPEX Helpdesk

GoalWhen your form app receives a new request, Make creates a ticket in IPEX Helpdesk and tags it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. Click the + on the empty canvas to add the first module. IPEX Helpdesk has no trigger, so this first module comes from another app.

  2. 02

    Start from your form app

    Search your form or chat app, pick its trigger for new entries and create its connection. Each entry it sends becomes a bundle, one item handed over to the next module.

  3. 03

    Add Create a Ticket

    Click the + on the right of the trigger, search IPEX Helpdesk and choose Create a Ticket. Connect your account, then map the data of the form entry into the fields Make displays.

  4. 04

    Tag the new ticket

    Add Add a Ticket Tag after it. Map the ticket returned by Create a Ticket, so the tag lands on the request you just opened and not on an older one.

  5. 05

    Test with Run once

    Submit a test entry in your form app, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open IPEX Helpdesk and check the ticket and its tag.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set the schedule: every 15 minutes by default, one minute at best on a paid plan. Switch the scenario on, and new requests reach your helpdesk without copy and paste.

Modules

What each IPEX Helpdesk module does

IPEX Helpdesk gives you 32 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

IPEX Helpdesk2

Add a Message

ActionIn the docs only

Posts a reply or a note into an existing ticket from your scenario, which keeps the whole conversation in IPEX Helpdesk even when the answer was written somewhere else.

When to use it
a customer answers through a chat tool outside the helpdesk and the text belongs on the ticket.
Watch out
map the ticket from an earlier module rather than typing a fixed value, or every message lands on the same request.
IPEX Helpdesk3

Add a Ticket Tag

ActionIn the docs only

Puts a label on one request, so the filters and queues of your helpdesk can sort it before anyone reads it.

When to use it
right after Create a Ticket, to mark the requests that came from a given form or channel.
Watch out
reuse the exact tag names your team already works with; a variant spelling means your filters miss the ticket.
IPEX Helpdesk4

Add a User into Customer

ActionIn the docs only

Attaches a person's user account to a customer company, so that person's requests sit under the right organization.

When to use it
a new employee at one of your clients writes in for the first time and you have just created their account.
Watch out
both records have to exist first, so chain Create an User Account or Search Customers before this module.
IPEX Helpdesk5

Add an User Tag

ActionIn the docs only

Labels a person rather than a ticket. The tag stays with that user across every request they send, which helps agents recognize a partner or a key contact at a glance.

When to use it
your CRM flags a contact as a key account and support should know it too.
Watch out
do not mix it up with Add a Ticket Tag, which only marks a single request.
IPEX Helpdesk6

Create a Customer

ActionIn the docs only

Adds a new customer company to IPEX Helpdesk from data held in another tool, so support has the account ready before the first ticket arrives.

When to use it
a deal is marked as won in your CRM.
Watch out
check with Search Customers first; a scenario that creates blindly can add the same company again on each run.
IPEX Helpdesk7

Create a Ticket

ActionIn the docs only

Opens a new support request with the content your scenario maps into it. Most scenarios built on this app revolve around this module.

When to use it
a form, a chat or a monitoring tool reports something that deserves a ticket.
Watch out
the module runs once per bundle, so a previous step that returns a long list opens one ticket for each item.
IPEX Helpdesk8

Create an Anonymous Ticket

ActionIn the docs only

Records a request without tying it to a user account, handy for visitors who never signed up to your support portal.

When to use it
a public contact form on your website, where most senders are prospects rather than clients.
Watch out
when the sender turns out to be a known client, Create a Ticket keeps the request with their account instead.
IPEX Helpdesk9

Create an User Account

ActionIn the docs only

Sets up an account for a person in IPEX Helpdesk straight from your scenario, so a new contact can be served without an agent entering them by hand.

When to use it
a new client signs and their team needs access to the portal.
Watch out
look the person up with Search User Accounts beforehand, since two records for one contact leave agents guessing.
IPEX Helpdesk10

Fulltext Search Tickets

ActionIn the docs only

Searches the text of your tickets for the words you give it and hands back the matches, the quickest route to past requests on the same topic.

When to use it
before opening a new ticket, to see whether the problem is already known.
Watch out
Make lists it as an action, not a search, so check with Run once whether the matches arrive as one bundle or several before you chain other modules.
IPEX Helpdesk11

Get Fields Description of Customer

ActionIn the docs only

Returns the description of the fields a customer record uses in your IPEX Helpdesk account, a map of what that record can hold.

When to use it
you are preparing an import and want to confirm which customer fields exist before mapping a spreadsheet.
Watch out
it describes the structure, not a company; to read an actual customer, use Get a Customer.
IPEX Helpdesk12

Get Fields Description of User Account

ActionIn the docs only

Tells your scenario how a user account is built in your helpdesk, so you know what data a person's record can receive.

When to use it
while setting up Import User Accounts or Create an User Account, when you are unsure a field exists on your side.
Watch out
run it with Run once during the build, then remove it, because it adds an operation to every run.
IPEX Helpdesk13

Get Track Time Records

ActionIn the docs only

Fetches the time entries logged in IPEX Helpdesk, which turns support effort into figures you can report or invoice.

When to use it
a project closes and the client asks how much support time went into their tickets.
Watch out
the records flow on as bundles; send them to a spreadsheet app to keep a copy instead of querying the helpdesk again.
IPEX Helpdesk14

Get a Customer

ActionIn the docs only

Reads one customer company in full, when your scenario already knows which one it wants.

When to use it
a ticket comes in and you need the client's details to decide who should handle it.
Watch out
it reads a single known customer; when all you have is a partial name, go through Search Customers, which can return zero or several matches.
IPEX Helpdesk15

Get a Ticket

ActionIn the docs only

Pulls the current state of one ticket, so later modules work with fresh data rather than what was true when the scenario started.

When to use it
before sending a status update to a client from an email or messaging app.
Watch out
the ticket reference has to come from an earlier module; Search Tickets finds it when you only know other details.
IPEX Helpdesk16

Get a Ticket Attachment

ActionIn the docs only

Retrieves a file attached to a ticket, so the scenario can store it, forward it or hand it to another app.

When to use it
invoices or screenshots sent by clients should also land in your shared drive.
Watch out
on the Free plan Make handles files up to 5 MB, so heavy attachments call for a paid plan.
IPEX Helpdesk17

Get an Operator Group

ActionIn the docs only

Reads one operator group, meaning a team of agents in IPEX Helpdesk, so its details can feed a later module.

When to use it
a routing scenario has to name the right team in a message sent through Slack or email.
Watch out
the module only reads the group and changes nothing, so it will not move a ticket to that team by itself.
IPEX Helpdesk18

Get an User Account

ActionIn the docs only

Returns the record of one person who has an account in your helpdesk, useful to personalize whatever the scenario does next.

When to use it
you want a contact's details before writing to them from a mailing tool.
Watch out
this module needs to know exactly which account to read; when you only partly know the person, Search User Accounts comes first.
IPEX Helpdesk19

Import Customers

ActionIn the docs only

Loads a batch of customer companies instead of creating them one at a time, a practical start when you move to IPEX Helpdesk from another tool.

When to use it
migrating your client list from a spreadsheet or a former helpdesk.
Watch out
confirm the expected structure with Get Fields Description of Customer, and try a small batch before the full list.
IPEX Helpdesk20

Import User Accounts

ActionIn the docs only

Brings a group of people into IPEX Helpdesk in one module, so a whole client team gets accounts in a single run.

When to use it
onboarding a new client whose contact list sits in a spreadsheet.
Watch out
Make's documentation says nothing specific about this module, so test with two or three rows and Run once before sending everyone.
IPEX Helpdesk21

Invite a User into Ticket

ActionIn the docs only

Brings another person into an ongoing conversation, for example a manager on the client side who should follow the exchange.

When to use it
a ticket is escalated and the client's account owner must be kept in the loop.
Watch out
pair it with Search User Accounts, and with Create an User Account when the search comes back empty.
IPEX Helpdesk22

List Country Codes

SearchIn the docs only

Gives back the country codes your helpdesk works with, a reference list rather than business data.

When to use it
your CRM stores full country names and they must be converted before Create a Customer.
Watch out
as a search it returns many bundles, so run it once while building to read the list instead of calling it on every run.
IPEX Helpdesk23

Search Customers

SearchIn the docs only

Finds the customer companies that match your criteria and returns zero, one or several of them. It is the safety check before any creation.

When to use it
a deal closes and you need to know whether the company already exists in your helpdesk.
Watch out
when nothing matches, the modules after it receive no bundle, so test that case with Run once as well.
IPEX Helpdesk24

Search Tickets

SearchIn the docs only

Returns the tickets that meet the conditions you set, each as a separate bundle you can count, export or update.

When to use it
a team lead wants every ticket of a key account copied to a shared sheet.
Watch out
if you are hunting for words inside the conversation, Fulltext Search Tickets is the better fit.
IPEX Helpdesk25

Search User Accounts

SearchIn the docs only

Checks which people already have an account and returns every match, which saves you from creating the same contact twice.

When to use it
just before Create an User Account or Invite a User into Ticket.
Watch out
several matches mean several bundles, and each one runs the next modules again; narrow the search before switching the scenario on.
IPEX Helpdesk26

Update Submitter

ActionIn the docs only

Changes the person recorded as the submitter of a ticket, useful when a request was opened on behalf of someone else.

When to use it
an assistant opens tickets for their manager, and the ticket should carry the manager's name.
Watch out
the new submitter should already have a user account, so look them up with Search User Accounts first.
IPEX Helpdesk27

Update Ticket Service

ActionIn the docs only

Sets or changes the service a ticket is filed under, so the request sits in the right part of your helpdesk.

When to use it
a web form lets clients pick a product, and that choice should decide the service.
Watch out
choose a service that already exists in your account, and confirm with Run once that IPEX Helpdesk accepts the value.
IPEX Helpdesk28

Update a Customer

ActionIn the docs only

Edits an existing customer company, keeping IPEX Helpdesk in line with the tool where your sales team keeps its records.

When to use it
a client changes address or contract in your CRM and support should see the change.
Watch out
the documentation does not say what happens to fields you leave empty, so check the mapping with Run once on a test customer.
IPEX Helpdesk29

Update a Ticket Category Items

ActionIn the docs only

Rewrites the category items of a ticket, the classification your team relies on to sort requests by topic.

When to use it
an earlier step in the scenario, an agent's choice in a form or a text classifier, has worked out what the request is about.
Watch out
category items belong to your own account, so read the values in IPEX Helpdesk before mapping them.
IPEX Helpdesk30

Update a Ticket Custom Form Data

ActionIn the docs only

Fills in or corrects the custom form of a ticket, the extra fields your team designed for its own process.

When to use it
an order number or a contract reference arrives later from another app and belongs on the ticket.
Watch out
custom forms differ from one account to the next; open yours in IPEX Helpdesk before mapping anything.
IPEX Helpdesk31

Update a Ticket Workflow

ActionIn the docs only

Moves a ticket along its workflow, the sequence of stages your helpdesk follows from a fresh request to a solved one.

When to use it
a field technician marks the job done in another tool and the ticket should advance.
Watch out
try it on a test ticket first and check the result in IPEX Helpdesk before you switch the scenario on.
IPEX Helpdesk32

Update an User Account

ActionIn the docs only

Edits the record of a person who already has an account, so the helpdesk keeps up when a contact changes role or company.

When to use it
your HR or CRM tool is the reference and IPEX Helpdesk should follow it.
Watch out
the scenario must know which account to edit; get it from Search User Accounts or Get an User Account first.
Need help

Need help automating IPEX Helpdesk with Make?

A person reads every message.

FAQ

IPEX Helpdesk and Make: frequent questions

01Is the IPEX Helpdesk Make integration free?
Yes. IPEX Helpdesk is a standard app, so its 32 modules work from the Make Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Each module execution counts as one operation on your plan. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to one minute and remove the cap on active scenarios. Your IPEX Helpdesk subscription is a separate matter that this page does not cover.
02What is needed to connect IPEX Helpdesk to Make?
An IPEX Helpdesk account and a Make account. Make's documentation lists no specific prerequisite for this app and gives no step-by-step connection guide, so the generic path applies: add any IPEX Helpdesk module, click Create a connection, name it if you like, then authorize Make on the IPEX Helpdesk page or paste the key the app provides, and click Save. The connection is created once and reused by all 32 modules. If saving fails, check the key or the authorization first.
03Does IPEX Helpdesk trigger Make scenarios in real time?
No, because IPEX Helpdesk has no trigger module in Make. It offers 28 actions and 4 searches, none of which watches the helpdesk for you. You still have two ways to start a scenario. The first is the schedule on the first module: every 15 minutes by default on a new scenario, one minute at best on a paid plan. The second is the trigger of another app; when that trigger is instant, the app calls Make through a webhook as soon as something happens there, and the IPEX Helpdesk modules follow.
04What if an IPEX Helpdesk module is missing in Make?
It depends on what is missing. IPEX Helpdesk has no Make an API Call module, so Make cannot send a custom request to its API the way it does for some apps. Check the 32 existing modules first: tickets, customers, user accounts, tags, attachments and time records are covered. Make marks its documentation for this app as limited, so a test with Run once is the surest way to see what a module returns. When a need is still not covered, the help form at the bottom of this page reaches the team, which can look at your case.
05Make or n8n for IPEX Helpdesk?
It depends on your criteria, not on a winner. On Make, IPEX Helpdesk comes with 32 ready modules, a visual editor and a Free plan with 2 active scenarios, enough to test a first ticket flow. Many apps also have an n8n node, but this page does not confirm one for IPEX Helpdesk, so check that before you compare. Then list the modules you actually need, decide who on your team will maintain the scenario, and see which editor that person finds easier to read. The comparison linked earlier on this page puts the two tools side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations