Resources · Make integration

HappyFox Help Desk Make integrationAutomate HappyFox Help Desk with Make.

Want every new support ticket to start work on its own? The HappyFox Help Desk Make integration gives you 8 modules: 1 instant trigger, 6 actions and 1 search. This page walks support leads through the connection, a first scenario and each module.

Try the HappyFox Help Desk integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the HappyFox Help Desk Make integration do?

It links your HappyFox account to Make, a no-code tool where you build a scenario (the automation itself, a chain of steps). Each step is a module: HappyFox can start the scenario the moment a ticket is created, then Make can open tickets, look them up, or post notes and replies on them.

Tickets from anywhere else. A form, a spreadsheet row or an email parsed by another app can become a HappyFox ticket through Create a Ticket. Nobody has to retype the request, and it lands in the same queue as the rest.

Context for the agent before they read. Watch New Ticket fires as soon as a ticket is created. Chain it with Search Tickets to find earlier requests, then write what you found with Add a Staff Private Note, so the agent opens a ticket that already has its history attached.

Replies driven by other tools. When an order ships or a bug is closed in your tracker, Add a Staff Update can post the news on the matching ticket, found first with Get a Ticket or a search.

What the listed modules do not cover, Make an API Call can reach through the HappyFox API, with the same connection. The Make documentation for this app lists no specific limits, so check the HappyFox side for anything critical.

New to Make? Our Make training starts from zero, and the Make pricing guide explains how plans count usage. Weighing another tool? Read n8n vs Make.

Connect

How do you connect HappyFox Help Desk to Make?

  1. 01

    Create an API key in HappyFox

    In HappyFox, open Apps > Goodies > API. Click Enable if the API is off, then the + sign. Give the key a name and click Add new API key.

  2. 02

    Copy both keys

    Hover over the new key's row and click see auth code. A slider opens with two values: the API key and the Auth key. Copy both, Make asks for each of them.

  3. 03

    Create the connection in Make

    Add any HappyFox module to your scenario and click Create a connection. A connection is your HappyFox account linked to Make once, then reused by every HappyFox module. Name it if you like, paste the two keys and save.

First scenario

Your first scenario with HappyFox Help Desk

GoalWhen a customer opens a ticket in HappyFox Help Desk, Make adds a private staff note with the triage checklist your team follows.

  1. 01

    Start a blank scenario

    From the Scenarios page, create a new scenario and click the big +. Type HappyFox Help Desk and pick Watch New Ticket as the first module.

  2. 02

    Link the webhook and your account

    Click Create a webhook, then Create a connection and paste your API key and Auth key. HappyFox will now call Make each time a ticket is created.

  3. 03

    Add the private note

    Click the + on the right of the trigger and choose Add a Staff Private Note. Map the ticket from the trigger, then type the checklist agents should run through.

  4. 04

    Test with Run once

    Click Run once, then open a test ticket in HappyFox. Each module shows the bundle it received (one bundle here, the new ticket), so you can check the note landed where it should.

  5. 05

    Switch it on

    Turn the scenario on. Since the trigger is instant, it runs whenever HappyFox reports a ticket, and each module run counts as one operation on your Make plan.

Triggers

What can start a HappyFox Help Desk scenario?

1 module starts a scenario when something happens in HappyFox Help Desk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HappyFox Help Desk as soon as it happens.

HappyFox Help Desk1Watch New Ticket

Watch New Ticket

Instant trigger

In Make“Triggers when a new ticket has been created.”

Gives your scenario a starting point the moment someone opens a ticket in HappyFox Help Desk. Every module you place after it receives that ticket as one bundle, the unit of data Make passes along.

How it fires
instant: the app calls Make through a webhook as soon as it happens, which is the lightning badge you see on the module.
When to use it
any flow that should react to fresh requests, such as posting a triage note, alerting a team channel through another app or copying the ticket into a reporting sheet.
Watch out
click Create a webhook before Create a connection, otherwise the trigger has nothing to listen on.
Modules

What can Make do in HappyFox Help Desk?

HappyFox Help Desk gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HappyFox Help Desk1

Add a Staff Private Note

Action

In Make“Adds a staff private note.”

Leaves an internal note from staff on an existing ticket, so the next agent reads the background your scenario gathered instead of digging for it.

When to use it
right after Watch New Ticket or Search Tickets, to paste earlier requests, an order status pulled from another app or a checklist.
Watch out
pick this one, not Add a Staff Update, when the text is meant for the team; confirm in HappyFox who can read private notes.
HappyFox Help Desk2

Add a Staff Update

Action

In Make“Adds a staff update.”

Posts a staff update on a ticket, which is how your automation can move a conversation forward when something changes outside HappyFox.

When to use it
a parcel ships, a refund goes through or a bug closes in another tool, and the ticket tied to it should say so without an agent copying the news by hand.
Watch out
find the right ticket first with Get a Ticket or Search Tickets, or the update lands on the wrong request.
HappyFox Help Desk3

Add a User Reply

Action

In Make“Adds a user reply.”

Records a reply on the user side of a ticket, which keeps follow-ups from customers in the same thread even when they arrive through another channel.

When to use it
a customer answers by form, chat or a second inbox handled in another app, and the message belongs on the ticket already open for them.
Watch out
this is the customer's voice on the ticket; for anything your team says, use Add a Staff Update instead.
HappyFox Help Desk4

Create a Ticket

Action

In Make“Creates a ticket.”

Opens a brand-new ticket in HappyFox Help Desk from data that started elsewhere, so every request ends up in one queue your agents already work from.

When to use it
a contact form, a new spreadsheet row or a message caught by another app should become a support request without anyone retyping it.
Watch out
if the same scenario also uses Watch New Ticket, the tickets you create will fire it, so filter them out to avoid a loop.
HappyFox Help Desk5

Get a Ticket

Action

In Make“Gets a ticket.”

Fetches one ticket you already know, so later modules can read its current state instead of relying on what an older module passed along.

When to use it
another app stores the HappyFox ticket reference, and your scenario needs the ticket itself before deciding whether to post an update or a note.
Watch out
it works on one known ticket; when you only have a customer or a keyword to go on, Search Tickets is the right module.
HappyFox Help Desk6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the HappyFox API to your scenario, with the connection you already set up, for everything the other seven modules leave out.

When to use it
you need an endpoint that has no dedicated module and you are comfortable reading the HappyFox API documentation to build the request.
Watch out
this module gives no dropdowns or field lists, so you shape the request yourself; test it with Run once before going live.
HappyFox Help Desk7

Search Tickets

Search

In Make“Searches for tickets.”

Looks through your HappyFox tickets and hands back the matches, which is how a scenario finds history it was not told about in advance.

When to use it
before adding a note or an update, to check whether this customer already has open or past requests.
Watch out
a search can return zero, one or several bundles, and each following module runs once per bundle, so plan for an empty result and for many.
Need help

Need help automating HappyFox Help Desk with Make?

A person reads every message.

FAQ

HappyFox Help Desk and Make: common questions

01Is the HappyFox Help Desk Make integration free?
Yes, on the Make side. HappyFox Help Desk is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. You still need an active HappyFox account, which HappyFox bills on its own terms.
02What do you need to connect HappyFox Help Desk to Make?
An active HappyFox account with its API feature turned on, plus two values from it: an API key and an Auth key. Both come from Apps, Goodies, API in HappyFox, where you create a key and click see auth code to reveal them. In Make, you add a HappyFox module, click Create a connection and paste the two keys. For the instant trigger, click Create a webhook before creating the connection. One connection then serves all 8 modules.
03Does the HappyFox Help Desk trigger in Make react in real time?
Yes. Watch New Ticket is an instant trigger: HappyFox calls Make through a webhook as soon as a ticket is created, instead of Make checking on a schedule. That is the lightning badge on the module. It is the only trigger this app offers, so a scenario that must react to replies or status changes has to start another way, for example from a schedule on a Search Tickets module or from a trigger in another app.
04What if a HappyFox module is missing in Make?
Use Make an API Call. It reaches any endpoint of the HappyFox API with the connection you already have, so an operation without its own module is still within reach. You write the request yourself, following the HappyFox API documentation, and test it with Run once. The Make documentation for HappyFox lists no specific limits on the modules, so check the HappyFox documentation for anything critical to your workflow before relying on it.
05Should you use Make or n8n for HappyFox Help Desk?
It depends on the tool your team already knows and where your other automations live. On Make, this app offers 8 modules, including an instant trigger for new tickets and an API call module for the rest. The same app often has an n8n node as well, so compare the modules each side offers for the operations you need, then pick the editor your team is most at ease with. The comparison page linked above goes through both tools.
Same platform

Other docs you might need on this stack.

Browse all integrations