- Home
- Resources
- Integrations
- FreeScout
FreeScout Zapier integrationAutomate FreeScout with Zapier.
FreeScout Zapier integration: 1 trigger, 1 action, 0 searches. A new conversation in your helpdesk can start an automation the moment it lands, and any other app can open a conversation for you, with no code to write on either side.
Verified Trustpilot reviews · AI, automation & growth agency
What the FreeScout Zapier integration does for your helpdesk
The FreeScout Zapier integration links your open source helpdesk to the other tools your team runs. It works in two directions only: a new conversation in FreeScout can kick off work elsewhere, and a request collected elsewhere can become a FreeScout conversation. That is the whole surface, and it is enough for most support teams.
Three results people usually build first. A support log that fills itself: Conversation Created adds a row to a sheet each time a ticket opens, so a manager can count volume without logging into the helpdesk. A heads-up in the team chat: the same trigger posts a short message to a channel, which helps when nobody keeps the inbox open all day. One queue for every request: Create Conversation turns a web form answer, a shop complaint or a CRM note into a conversation in the right mailbox, next to the emails.
Now the limits, because they matter before you start. Zapier offers FreeScout a single trigger and a single action. There is no search step, so a Zap cannot look up an existing customer or conversation first. Nothing fires when a conversation is updated, replied to or closed: only creation counts. And Create Conversation always opens a new thread; it never adds a reply to one that already exists.
If those gaps block your scenario, the FreeScout Make integration page covers the same helpdesk on the other platform, and Make vs Zapier is the comparison to read next.
Zapier vocabulary in one minute
Eight words come back on every Zapier page. Here they are in plain English, once.
- Zap
- The automation you assemble in Zapier: one trigger, followed by one or more actions that run each time that event occurs.
- Trigger
- The event in an app that kicks off the Zap. Once the Zap is switched on, Zapier sits and waits for it to happen.
- Action
- What the Zap does once it has started. With FreeScout, that can be opening a conversation for you, or anything another app does with a new ticket.
- Task
- What Zapier bills. One action that completes successfully equals one task, and your plan is a count of those.
- Polling vs instant
- Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself the second the event happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets a condition you set, and halts it otherwise.
- Search step
- A step that looks up an item already stored in an app so later steps can reuse it. FreeScout has none on Zapier.
- Connection
- Your FreeScout account linked to Zapier once, then reused by every step of every Zap that touches FreeScout.
What a FreeScout Zap really costs
Watching for new conversations is free. Zapier only bills the actions that succeed.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The trigger never uses a task, however many conversations open. Each successful action counts as one task, so a Zap with two actions burns twice as much per run, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: add a filter or a second action and you need a paid plan. FreeScout is not a premium app, so it runs on the free plan.
Connect FreeScout to Zapier in three steps
- 01
Open the Apps page
Open the Apps page of your Zapier account, then hit + Add connection. In the dialog that pops up, type FreeScout in the search box and pick it from the list of results.
- 02
Sign in to FreeScout
Click Add connection. A new tab asks you to sign in to your FreeScout account. Use the account that can see the mailboxes you plan to automate, not a personal one with partial access.
- 03
Grant access
Approve the access Zapier asks for. The connection is saved once and every FreeScout step reuses it, in this Zap and the next. You need an account on the helpdesk, plus rights on any mailbox you do not own.
Your first Zap: bug reports from FreeScout into Asana
GoalA small software studio answers users in FreeScout and wants every conversation that reports a bug to become a task in the developers' Asana project.
- 01
Set the trigger
In the editor, pick FreeScout and the Conversation Created event as the start, then select the FreeScout connection you made in the previous section.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent conversations of the account, so you map the next steps on a real ticket rather than a blank template.
- 03
Add the filter
Add a Filter step from the plus icon. Pick the value you spotted in the test that tells a bug from a question, choose a text rule, and type the word to match.
- 04
Add the Asana task
Pick Asana and Create Task. Choose the developers' project, then build the task name from the conversation details the test brought back.
- 05
Test, then publish
Test each step and open Asana to check the task looks right. Then click Publish. The filter makes this Zap multi-step, so it needs a paid plan.
The FreeScout trigger
1 event starts a Zap when something happens in FreeScout, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Conversation Created
Instant triggerIn Zapier“Triggers when a new conversation is created.”
This trigger starts your Zap each time a new conversation appears in FreeScout. The steps that follow work with the details you saw in the test sample, so map them from a real conversation rather than guessing.
The FreeScout action
FreeScout gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Conversation
ActionIn Zapier“Create a new Conversation.”
Opens a fresh conversation in the FreeScout mailbox you choose, with a subject, a first message and the customer it belongs to.
When a FreeScout Zap breaks
Zapier attaches no help article to FreeScout, so these are the general limits that hit a helpdesk Zap.
Most failures come from timing and loops, not from FreeScout itself. If a Zap still misbehaves after these checks, the Zapier troubleshooting page walks through the usual fixes.
Old conversations never come through
The Zap reacts only to conversations created after you publish it. Everything already sitting in FreeScout stays put; moving that backlog is a separate job.A Zap that feeds itself
Pairing Conversation Created with Create Conversation in the same helpdesk makes every new conversation spawn another one, and your task count drains fast.A sudden flood gets held back
After a bulk import or a migration, a huge batch of new conversations can be paused by Zapier's flood protection instead of running straight through.The filtered Zap stops on the free plan
A filter, a second action or a search turns the Zap multi-step. The free plan only builds two-step Zaps, so a filtered support Zap needs a paid plan.
Need help automating FreeScout with Zapier?
A person reads every message.



