Resources · Make integration

FreeScout Make integrationAutomate FreeScout with Make.

Can Make open, route and follow up your FreeScout tickets without code? The FreeScout Make integration gives you 3 modules: one instant trigger and two actions. It suits support leads who run a FreeScout helpdesk, and this page takes you from the API key to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FreeScout Make integration do for your helpdesk?

The FreeScout Make integration links your helpdesk to Make, a no-code tool where you build a scenario: the automation itself, a chain of steps. Each step is a module. Here you get one trigger that reacts to conversation events in FreeScout and two actions that write back into it. Your account is linked once, as a connection, and every module reuses it.

Every assigned or answered ticket reaches the right person. Watch Conversations fires when a conversation is created, assigned, moved, changes status, or gets a customer reply, an agent reply or an internal note. Pass the ones that matter to the tool your team already reads.

Requests from outside become FreeScout tickets. A web form, a spreadsheet row or a message in another app can start the scenario, and Create a Conversation turns it into a ticket your agents can answer.

A deleted conversation leaves a trace. Deletions come through too. Log them elsewhere before the context is gone.

What the app does not offer: there is no search module, only one trigger and two actions. For the rest, Make an API Call reaches the FreeScout API with the same connection. The Make docs for FreeScout are flagged as AI-generated, so confirm important details with FreeScout. The same app may also have an n8n node, and the n8n vs Make comparison helps you choose. Before a paid plan, read Make pricing; if a run fails, start with Make troubleshooting.

Connect

How do you connect FreeScout to Make?

  1. 01

    Get the API key from FreeScout

    Your FreeScout needs the API and Webhooks module installed. Open Manage, then Settings, then the API & Webhooks tab, and copy the key shown there. Also copy the full address of your FreeScout from the browser bar: that is your Helpdesk URL.

  2. 02

    Add a FreeScout module and start the connection

    In your scenario, add a FreeScout module and click Create a connection. With Watch Conversations, which carries the instant tag, click Create a webhook first, then Create a connection. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste your credentials and save

    Enter the Helpdesk URL and the API key you copied, or follow the instructions on screen. Make saves the connection, and every FreeScout module in your other scenarios can pick it from the list instead of asking again.

First scenario

Build your first FreeScout scenario

GoalWhen a request comes in through your web form, Make creates a conversation in FreeScout.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add its first module. That first bubble is the app where requests arrive, here your web form tool.

  2. 02

    Pick the starting app

    Search the form app by name, choose the module that watches new entries, and link your account with Create a connection. Make then lists the forms it can read.

  3. 03

    Add Create a Conversation

    Click the + on the right of the first module, search FreeScout and pick Create a Conversation. Select your FreeScout connection, then fill each field by mapping the data the form module received.

  4. 04

    Test with Run once

    Click Run once, then send a test entry through the form. Each module shows the bundles it received (a bundle is one item, here one request), and a new ticket should appear in FreeScout.

  5. 05

    Set the schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default in a new scenario, and switch the scenario on. Each module run on a bundle is an operation, the unit Make counts on your plan.

Triggers

What starts a FreeScout scenario

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

FreeScout1Watch Conversations

Watch Conversations

Instant trigger

In MakeTriggers when one of the following events occurs: convo.assigned, convo.created, convo.deleted, convo.moved, convo.status, convo.customer.reply.created, convo.agent.reply.created, convo.note.created.

Watch Conversations tells Make that something just changed on a conversation: it was created, assigned, moved or deleted, its status changed, or it got a customer reply, an agent reply or an internal note. Each of these events can start your scenario.

How it fires
instant, FreeScout calls Make through a webhook as soon as the event happens. In the editor, the module shows a lightning badge.
When to use it
a customer answers an open ticket and the assigned agent should hear about it in the channel the team watches.
Watch out
click Create a webhook before Create a connection, and check in the module settings which events you can leave out: each one that reaches Make runs the scenario.
Modules

What FreeScout can do in a scenario

FreeScout gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

FreeScout1

Create a Conversation

Action

In MakeCreates a new conversation.

Create a Conversation opens a new ticket in FreeScout from data another module brings in, so requests collected elsewhere land where your agents already work.

When to use it
a quote request or an order problem reported in another tool should become a ticket someone owns.
Watch out
if the same scenario starts on Watch Conversations with the created event, each new ticket would start it again, so keep those two in separate flows.
FreeScout2

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the way out when the two ready-made modules fall short: it calls any endpoint of the FreeScout API with the connection you already set up, so there is no second login to manage.

When to use it
you need something the FreeScout API offers that has no dedicated module, knowing the app has no search module at all.
Watch out
you write the request yourself, so try it with Run once on a harmless call before you map real data into it.
Need help

Need help automating FreeScout with Make?

A person reads every message.

FAQ

FreeScout and Make: common questions

01Is the FreeScout Make integration free?
Yes, on the Make side. FreeScout is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, called credits, per month. Your FreeScout subscription is a separate matter, covered by FreeScout's own pricing page.
02What do you need to connect FreeScout to Make?
An active FreeScout account with the API and Webhooks module installed, plus two values copied from it. The first is the Helpdesk URL, the full address of your FreeScout as shown in the browser bar. The second is the API key, under Manage, then Settings, then the API & Webhooks tab. In Make, add a FreeScout module, click Create a connection, give it an optional name and paste both values. For the instant trigger, click Create a webhook first, then Create a connection.
03Does the FreeScout trigger in Make fire in real time?
Yes. Watch Conversations is an instant trigger: FreeScout calls Make through a webhook as soon as a watched event happens. That covers a new conversation, an assignment, a move, a status change, a deletion, a reply from a customer or an agent, and an internal note. Each event reaching Make runs the scenario and uses operations, so check in the module settings which events you can leave out. In the editor, an instant trigger shows a lightning badge.
04What if a FreeScout module is missing in Make?
Use Make an API Call. The app lists one trigger and two actions, with no search module, so anything else goes through this module: it calls any endpoint of the FreeScout API with the connection you already created. You write the request yourself, so test it with Run once before switching the scenario on. The Make documentation for FreeScout is marked as AI-generated and may contain mistakes, so confirm important details with FreeScout directly.
05Make or n8n for FreeScout?
It depends on your own criteria, and this page does not rank the two. On Make, FreeScout comes with 3 modules: an instant trigger on conversation events, Create a Conversation and Make an API Call, all available from the Free plan. Apps like this one often have an n8n node too, so check whether FreeScout has one before you decide. Then compare both tools on what matters to you: the modules your flow needs, the tool your team already uses, and the plan limits listed above.