FreJun Make integrationAutomate FreJun with Make.
What happens to a call once your rep hangs up? The FreJun Make integration gives you 7 triggers that pick up calls, summaries, notes and recordings. This page shows how to link your account, build a first scenario and choose the right trigger.
Verified Trustpilot reviews · AI, automation & growth agency
What can the FreJun Make integration automate?
The FreJun Make integration lets a call event in FreJun start an automation in Make, called a scenario: a chain of bricks, or modules, where each one hands its result to the next. On the FreJun side, every module is a trigger, so FreJun is where the scenario begins and another app finishes the job.
Keep the CRM up to date after each call. Watch Call Outcome Change starts the scenario when a call's outcome moves, so the next module can update the deal or the contact in the tool your sales team already uses.
Share what was said without replaying the call. Watch Call Summary and Watch Call Notes Updated pass the written side of a call to a channel, a document or a ticket, so a manager reads the gist instead of listening to the whole conversation.
File every recording in the right place. Watch Call Recording picks up recordings so a storage app can keep them next to the customer record.
What the integration does not do: FreJun has no action or search module in Make, no instant trigger and no Make an API Call module. Make never places a call or edits a FreJun record for you; it only reacts to what FreJun already holds. Make's own documentation also flags that its FreJun page was written with AI help, so check a detail with FreJun when it matters. If you are weighing Make against n8n for this kind of flow, the n8n vs Make comparison lays out the criteria, and the Make review helps you judge the editor before you commit. Stuck on a run that fails? Start with Make troubleshooting.
How do you connect FreJun to Make?
- 01
Register an OAuth app in FreJun
Log in to FreJun, open Settings, then the Developer tab. Click Create App, or open the OAuth app you already have, and copy the Client ID and the Client secret shown on screen.
- 02
Add a FreJun module in Make
In your scenario, add any FreJun trigger and click Create a connection. A connection is your FreJun account linked to Make once, then reused by all 7 FreJun modules. The Connection name field is optional.
- 03
Paste the credentials and confirm
Enter the Client ID and Client secret you copied, or follow the instructions Make displays, and save. Once the connection exists, Make can read your FreJun data and list what the module needs.
Your first scenario with FreJun and Make
GoalWhen FreJun has a new call summary, Make passes it to the app where your team follows up on calls.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the big + to place the first module.
- 02
Pick Watch Call Summary
Search for FreJun, choose Watch Call Summary and select the connection you created. This trigger opens the flow: each summary it finds becomes one bundle, one item passed to the next module.
- 03
Add the follow-up app
Click the + on the right of the trigger and pick the app where summaries should land. Map the data coming from Watch Call Summary into its fields.
- 04
Test with Run once
Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check that the summary reached the second app.
- 05
Schedule and switch it on
Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or change it, then switch the scenario on so it runs without you.
Which FreJun triggers can start a scenario?
7 modules start a scenario when something happens in FreJun. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by FreJun as soon as it happens.
Watch Call Insights
triggerIn the docs onlyThis trigger starts a scenario from the insights FreJun attaches to calls. Make's documentation lists it without a description, so what it returns is best seen on a first test.
Watch Call Notes Updated
triggerIn the docs onlyPick this one when the notes a rep types on a call matter more than the call itself. Judging by its name, it reacts when those notes change in FreJun.
Watch Call Outcome Change
triggerIn the docs onlyYour pipeline moves the moment a call's outcome moves. The name of this trigger points to exactly that: a change in the outcome recorded for a call.
Watch Call Reason Change
triggerIn the docs onlyHere the scenario follows why people call rather than how the call ended. As its name says, the trigger watches changes to the reason attached to a call.
Watch Call Recording
triggerIn the docs onlyRecordings stop living only inside FreJun. Going by its name, this trigger hands each call recording it finds to the rest of your scenario, ready to be stored or shared.
Watch Call Status
triggerIn the docs onlyYou get a signal each time a call's status moves, which is the broadest of the seven triggers. Its name is the only hint the documentation gives.
Watch Call Summary
triggerIn the docs onlyJudging by its name, a written recap of the call lands in your scenario without anyone replaying the audio. This is the trigger to start with if the team reads more than it listens.
Need help automating FreJun with Make?
A person reads every message.
