- Home
- Resources
- Integrations
- FreeScout
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 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.
How do you connect FreeScout to Make?
- 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.
- 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.
- 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.
Build your first FreeScout scenario
GoalWhen a request comes in through your web form, Make creates a conversation in FreeScout.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Watch Conversations
Instant triggerIn Make“Triggers 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.
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.
Create a Conversation
ActionIn Make“Creates 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.
Make an API Call
ActionIn Make“Performs 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.
Need help automating FreeScout with Make?
A person reads every message.