Resources · Make integration

HappyFox Chat Make integrationAutomate HappyFox Chat with Make.

Can a missed chat stop slipping through the cracks? The HappyFox Chat Make integration gives you 3 modules: 2 instant triggers and 1 open API action. This guide is for support leads new to Make, and it takes you from connection to a live scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the HappyFox Chat Make integration do?

The HappyFox Chat Make integration links your chat account to Make so that the end of a conversation, a chat no agent picked up, or a message left while everyone was offline can start an automation on its own. Make calls that automation a scenario: a chain of modules, each one a single step handled by one app.

Never lose an after-hours request. Watch New Offline Message starts your scenario as soon as a visitor writes while all agents are away. From there, the message can be copied into your helpdesk, a shared inbox or a spreadsheet, so the morning shift starts from a list instead of a surprise.

Follow up on chats nobody answered. Watch New Finished or Missed Chat fires on two events: a conversation that ends, and an incoming request that no agent picked up. Filter on the missed ones and you get a callback queue built without anyone copying names by hand.

Reach what the listed modules don't cover. Make an API Call sends an authorized request to the HappyFox Chat API with the connection you already set up. It is the escape hatch when you need an endpoint that has no ready-made module.

Worth knowing before you start: the app has no search module and no scheduled trigger, so everything begins with an event in HappyFox Chat. If you're still choosing a tool, the n8n vs Make comparison lays out the differences, and the Make pricing page explains how operations are counted on each plan. Stuck on a failing run? Our Make troubleshooting guide covers the usual errors.

Connect

How do you connect HappyFox Chat to Make?

  1. 01

    Add a HappyFox Chat module

    In your scenario, click the +, search for HappyFox Chat and pick any of its modules. Then click Create a connection. A connection is your HappyFox Chat account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    Give the connection a name you'll recognize later, for example the account or brand it belongs to. The step is optional, but it saves guesswork the day you run two HappyFox Chat accounts side by side.

  3. 03

    Authorize and save

    Make then either opens a HappyFox Chat page asking you to approve access, or asks for the key your account gives you. Complete whichever one shows up, then click Save. The connection now appears in every HappyFox Chat module.

First scenario

Build your first scenario with HappyFox Chat

GoalWhen a visitor leaves a message while all agents are offline in HappyFox Chat, Make picks it up and sends a request to the HappyFox Chat API.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. An empty canvas appears with a single + in the middle: that's where your first module goes.

  2. 02

    Add the offline message trigger

    Click the +, search for HappyFox Chat and choose Watch New Offline Message. Select the connection you created, or click Create a connection if you haven't done it yet.

  3. 03

    Add the API call

    Click the + on the right of the trigger and pick Make an API Call. Fill in the request, and map values from the offline message by clicking the fields the trigger received.

  4. 04

    Test with Run once

    Click Run once, then leave a test message on your chat widget while agents are offline. Open each module's bubble to read the bundle it received, that is, the single item passed from one module to the next.

  5. 05

    Switch it on

    When the test looks right, turn the scenario on. Because the trigger is instant, HappyFox Chat alerts Make by webhook whenever a new offline message arrives, with no polling in between.

Triggers

What can start a HappyFox Chat scenario?

2 modules start a scenario when something happens in HappyFox Chat. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HappyFox Chat as soon as it happens.

HappyFox Chat1Watch New Finished or Missed Chat

Watch New Finished or Missed Chat

Instant trigger

In Make“Triggers when a chat conversation ends or no agents pickup an incoming chat request.”

This trigger hands your scenario every conversation that has just closed, along with every incoming chat request that no agent picked up. One module, two situations, so a single scenario can cover both the wrap-up of good chats and the rescue of lost ones.

How it fires
instant, HappyFox Chat calls Make through a webhook as soon as the chat ends or goes unanswered.
When to use it
you want each missed request turned into a callback task for the next available agent.
Watch out
finished and missed chats arrive through the same trigger, so add a filter after it if your next steps should only handle one of the two.
HappyFox Chat2Watch New Offline Message

Watch New Offline Message

Instant trigger

In Make“Triggers when a visitor leaves a message when all agents are offline.”

Here your scenario receives the message a visitor types into the widget when every agent is offline. It turns the quiet hours into a queue your team can pick up, instead of messages sitting unseen in the chat history.

How it fires
instant, HappyFox Chat alerts Make by webhook the moment the visitor sends the message.
When to use it
your support team works set hours and you want after-hours questions routed to the helpdesk or inbox they check first.
Watch out
this trigger only sees offline messages; chats that happen while agents are online go through Watch New Finished or Missed Chat.
Modules

What else can HappyFox Chat do in Make?

HappyFox Chat gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

HappyFox Chat1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you send any authorized request to the HappyFox Chat API, reusing the connection you already created, so no extra login is needed. It covers what the two triggers leave out.

When to use it
you need an endpoint of the HappyFox Chat API that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the HappyFox Chat API reference open while you fill it in.
Need help

Need help automating HappyFox Chat with Make?

A person reads every message.

FAQ

HappyFox Chat and Make: common questions

01Is the HappyFox Chat Make integration free?
Yes. HappyFox Chat is a standard app, so its 3 modules work on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the scenario cap, allow runs as close as 1 minute apart and extend execution to 40 minutes. Every module run counts as an operation against your monthly credits.
02What do you need to connect HappyFox Chat to Make?
A HappyFox Chat account and a Make account. The HappyFox Chat documentation lists no specific prerequisite and no dedicated connection steps, so the generic Make flow applies: add a HappyFox Chat module, click Create a connection, optionally name it, then approve access on the HappyFox Chat page or paste the key your account provides, and click Save. After that, all three modules reuse the same connection. If a module shows no connection to pick, the Save click was probably skipped: reopen the connection and finish it.
03Do HappyFox Chat triggers in Make react in real time?
Yes. Both triggers are instant. Watch New Finished or Missed Chat and Watch New Offline Message are called by HappyFox Chat through a webhook as soon as the event happens, so Make doesn't wait for the default 15 minute schedule of a new scenario. To check the setup before going live, click Run once and trigger a test chat, then read the bundle each module received. Each trigger call then runs the scenario on the bundle HappyFox Chat sent.
04What if the HappyFox Chat module you need is missing in Make?
Use Make an API Call. It sends any authorized request to the HappyFox Chat API with the connection you already have, so an endpoint without a ready-made module is still reachable from your scenario. The HappyFox Chat documentation gives no numeric limits for these modules. The trade-off is that you build the request yourself, so check the API reference of HappyFox Chat for the path and parameters. Test each new request with Run once before you switch the scenario on.
05Should you use Make or n8n for HappyFox Chat?
It depends on what your team already runs. In Make, HappyFox Chat offers 2 instant triggers plus Make an API Call, which is enough to react to finished, missed and offline chats and to reach the rest of the API. n8n often has a node for the same app, so check its catalog before deciding. Pick the tool where your other automations already live, since maintaining one platform is simpler than two.