Resources · Make integration

Freshsales Make integrationAutomate Freshsales with Make.

Can Make keep your Freshsales pipeline moving while you sell? The Freshsales Make integration ships 56 modules: 8 triggers, 35 actions and 13 searches. This guide is for sales and ops people who know the CRM, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Freshsales Make integration automate?

The Freshsales Make integration links your CRM account to Make so records move on their own: a new lead can spawn a task, a won deal can update an account, a call can be logged from another tool. You build it as a scenario, the automation you assemble in Make from modules, each one a single brick such as a trigger, an action or a search.

No lead left without a next step. Watch New Leads picks up every lead added to Freshsales, and Create a Task hands it to a rep with the lead's details mapped in. The follow-up exists before anyone has to remember it.

A clean handover from marketing to sales. When a lead qualifies in another tool, Search Leads finds the matching record, Convert a Lead turns it into a contact, and Create a Deal opens the opportunity in the same run.

Call history that writes itself. Calls made outside Freshsales can land in the CRM through Create a Manual Call Log, attached to the right contact or account, so the timeline stays complete for the next person who opens the record.

Make does not cover every corner of the Freshsales API with a ready module. For the rest, Make an API Call reuses your connection to reach any endpoint. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and the Make review gives the full picture of the platform.

Connect

How do you connect Freshsales to Make?

  1. 01

    Copy your API key from Freshsales

    In Freshsales, click the Profile icon, open Settings, then the API SETTINGS tab. Complete the captcha when asked and copy the value shown in Your API key. You need an active Freshsales CRM account for this screen to exist.

  2. 02

    Add a Freshsales module in Make

    Open your scenario, click the +, search for Freshsales and pick any module. Click Create a connection. The Connection name field is optional; a name like Sales CRM helps when several accounts share one Make organization.

  3. 03

    Paste the credentials and save

    Enter the credentials you copied from Freshsales, or follow the on-screen instructions, then save. That connection, your Freshsales account linked to Make, is reused by every other Freshsales module you add later.

First scenario

Your first scenario: a task for every new lead

GoalWhen a new lead lands in Freshsales, Make creates a follow-up task for the sales team.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario. Make opens an empty editor with a single + in the middle: that is where your first module goes.

  2. 02

    Add Watch New Leads

    Click the +, search for Freshsales and choose Watch New Leads. Pick your connection, or click Create a connection if this is your first Freshsales module.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and pick Create a Task. Map the lead name into the task title so the rep knows at a glance who to call.

  4. 04

    Test with Run once

    Add a test lead in Freshsales, then click Run once. Open the bubble above each module to read the bundle it received, one lead in, one task out.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default. Switch the scenario on and new leads get their task without you.

Triggers

What starts a Freshsales scenario

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

Freshsales1Watch New Accounts

Watch New Accounts

Scheduled trigger

In MakeChecks if new account was created.

Every company you add to Freshsales as an account becomes a starting point for your scenario, so onboarding steps can kick off without anyone copying the name elsewhere. Each new account arrives as one bundle, the item passed on to the next module.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
when an account created by the sales team should open a folder, a project or a billing record in another tool.
Freshsales2Watch New Appointments

Watch New Appointments

Scheduled trigger

In MakeChecks if new appointment was created.

Meetings booked in Freshsales can feed the rest of your stack as soon as Make sees them. You get one bundle per new appointment, ready to send a reminder, prepare a brief or notify a manager.

How it fires
scheduled, Make checks the app on the scenario's schedule, so a meeting shows up at the next check rather than the second it is booked.
When to use it
when a booked demo should post a message to the team channel or add a prep task.
Freshsales3Watch New Contacts

Watch New Contacts

Scheduled trigger

In MakeChecks if new contact was created.

This trigger hands every newly created contact to your scenario, which keeps a mailing tool, a spreadsheet or a support desk aligned with the CRM. Each one travels as a bundle to the next module.

How it fires
scheduled, Make checks the app on the scenario's schedule; on the Free plan the shortest interval is 15 minutes.
When to use it
when a new customer contact needs a welcome email or a row in a shared sheet.
Freshsales4Watch New Deals

Watch New Deals

Scheduled trigger

In MakeChecks if new deal was created.

Opportunities opened in Freshsales reach Make one by one, with their details in the bundle, so finance or delivery hears about a deal from the moment it exists instead of at signature.

How it fires
scheduled, Make checks the app on the scenario's schedule, and paid plans can shorten the interval to 1 minute.
When to use it
when each fresh deal should alert a manager or open a draft quote elsewhere.
Watch out
it reacts to new deals only, not to a stage change on an existing one.
Freshsales5Watch New Events

Watch New Events

Instant trigger

In MakeTriggers when a webhook event occurs in a Freshsales Workflow.

Rather than waiting for Make to look, this trigger lets a Freshsales Workflow push an event to your scenario through a webhook. You decide in Freshsales which rule sends the event, and Make receives it right away.

How it fires
instant, Freshsales calls Make through a webhook as soon as the workflow event occurs.
When to use it
when timing matters, for example a deal moving to a stage your workflow watches.
Watch out
click Create a webhook before Create a connection when you add it.
Freshsales6Watch New Leads

Watch New Leads

Scheduled trigger

In MakeChecks if new lead was created.

Fresh prospects entering Freshsales, from a form, an import or a rep, start your scenario one lead per bundle. It is the natural entry point for routing, enrichment and follow-up automations.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes unless you change the clock on the module.
When to use it
when every lead should get an owner, a task or a message the moment the next check runs.
Freshsales7Watch New Sales Activities

Watch New Sales Activities

Scheduled trigger

In MakeChecks if new sales activity was created.

Sales activities logged in Freshsales can be mirrored into reporting or shared with other teams through this trigger, one activity per bundle.

How it fires
scheduled, Make checks the app on the scenario's schedule, so activities are collected in batches at each check.
When to use it
when a manager tracks activity in a spreadsheet or a dashboard fed outside the CRM.
Watch out
each activity picked up runs the following modules once, which costs operations.
Freshsales8Watch New Tasks

Watch New Tasks

Scheduled trigger

In MakeCheck if new task was created.

Tasks created in Freshsales can follow the rep outside the CRM: into a to-do app, a calendar or a chat message. Make passes each new task to the next module with its details.

How it fires
scheduled, Make checks the app on the scenario's schedule, which you set on the clock of this first module.
When to use it
when your team works from a task tool other than Freshsales and needs CRM tasks copied there without double entry.
Modules

What Freshsales can do in Make

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

Freshsales1

Convert a Lead

Action

In MakeConverts a lead to a contact.

Promotes a Freshsales lead to a contact in one step, so a qualified prospect moves to the customer side of the CRM without anyone retyping the record.

When to use it
right after a lead books a demo or accepts a quote, with the lead ID mapped from the trigger or a search.
Watch out
the module expects a lead ID; a contact ID gives it nothing to convert.
Freshsales2

Create a Contact

Action

In MakeCreates a new contact.

Adds a person to Freshsales as a contact from data collected anywhere else, a signed form, a paid order, a support ticket, so the CRM holds the customer before sales even looks.

When to use it
when the person is already a customer and does not need the lead stage.
Watch out
run Search Contacts first if the same email could arrive twice.
Freshsales3

Create a Deal

Action

In MakeCreates a new deal.

Opens a new opportunity in Freshsales, with the values you map from the previous modules, so revenue in progress appears in the pipeline the moment a buying signal shows up.

When to use it
after a quote request, a trial signup or a lead conversion in the same scenario.
Watch out
link it to the contact or account you just found or created, or the deal floats alone.
Freshsales4

Create a Lead

Action

In MakeCreates a new lead.

Drops a new prospect into Freshsales from a web form, an event list or an ad platform, which keeps every source of interest flowing into the same pipeline instead of scattered spreadsheets.

When to use it
when the person has not bought yet and sales still has to qualify them.
Watch out
check with Search Leads before creating, forms often get submitted twice.
Freshsales5

Create a Manual Call Log

Action

In MakeCreates a manual call log for new or existing lead/contact or an existing account.

Records a phone call in Freshsales for a new or existing lead or contact, or an existing account, so calls made through another phone tool still appear on the customer timeline.

When to use it
when your calling software sends call details after each conversation and reps forget to log them.
Watch out
for an account, the record must already exist in Freshsales.
Freshsales6

Create an Account

Action

In MakeCreates a new account.

Creates the company record in Freshsales, the account that contacts and deals hang from, so a new customer organization is set up the same way every time.

When to use it
when a signed contract or a new client in your billing tool should give sales a matching account.
Watch out
use Search Accounts first; two accounts for one company split the history.
Freshsales7

Create an Appointment

Action

In MakeCreates a new appointment.

Puts a meeting into Freshsales from a booking made elsewhere, so the rep sees the appointment on the right record and the CRM calendar matches reality.

When to use it
when prospects book through an external scheduling page and the meeting should appear in the CRM too.
Watch out
map the date and time from the booking tool rather than typing them into the module.
Freshsales8

Create a Note

Action

In MakeCreates a note for specific object.

Attaches a written note to a specific Freshsales record, which is the easiest way to leave context from another tool where the rep will read it.

When to use it
when a support ticket, a form answer or a survey reply should sit on the contact or deal it concerns.
Watch out
the note needs the record it belongs to, so map that ID from an earlier module.
Freshsales9

Create a Sales Activity

Action

In MakeCreates new Freshsales activity.

Logs a Freshsales sales activity from an event that happened outside the CRM, so managers count the work done wherever it took place.

When to use it
when a visit logged in a field app or a webinar attendance should show as activity on the customer record.
Watch out
map the customer record from an earlier module so the activity lands on the right timeline.
Freshsales10

Create a Task

Action

In MakeCreates a new task.

Gives a rep a concrete next step in Freshsales, with the context you map from the trigger, so follow-ups are created by the process and not by memory.

When to use it
after Watch New Leads, or when a customer event in another tool calls for a callback.
Watch out
map the lead or contact from the trigger so each task points to the person it concerns.
Freshsales11

Delete a Contact

Action

In MakeDeletes a specific contact.

Removes a contact from Freshsales when another system says the person should no longer be there, which helps keep the database clean after unsubscribes or data requests.

When to use it
when a deletion request is approved in your privacy or support process.
Watch out
treat it as permanent and confirm the right record with View a Contact before this module runs.
Freshsales12

Delete a Deal

Action

In MakeDeletes a specific deal.

Clears an opportunity out of Freshsales, useful when test deals or duplicates created by an import clutter the pipeline and skew forecasts.

When to use it
in a cleanup scenario that first lists or searches deals and keeps only the ones flagged as duplicates.
Watch out
a search can return several deals, so check what reaches this module with Run once first.
Freshsales13

Delete a Lead

Action

In MakeDeletes a specific lead.

Takes a lead out of Freshsales once it is clearly spam or no longer relevant, so reps work a list that deserves their time.

When to use it
when a form tool flags a submission as junk after the lead was already created.
Watch out
converting is the better route for a real prospect; deletion should only reach leads you mean to lose.
Freshsales14

Delete an Account

Action

In MakeDeletes a specific account.

Removes a company record from Freshsales, which matters when a merged or closed organization would otherwise keep appearing in account lists and assignments.

When to use it
when your billing or ERP system marks a client as removed and the CRM should follow.
Watch out
contacts and deals tied to that account deserve a look before the account disappears.
Freshsales15

Delete an Appointment

Action

In MakeDeletes a specific appointment.

Cancels a meeting on the Freshsales side when it was cancelled somewhere else, so the rep does not prepare for a call that will never happen.

When to use it
paired with a cancellation event from your booking tool, using the appointment ID you stored when it was created.
Watch out
without that stored ID the scenario cannot know which appointment to remove.
Freshsales16

Delete a Note

Action

In MakeDeletes a specific note.

Erases a note from a Freshsales record, handy when an automated note carried wrong or sensitive content and should not stay visible to the team.

When to use it
as a correction step after a scenario posted notes with a mapping mistake.
Watch out
you need the note ID itself, so keep it from the Create a Note output when you plan cleanups.
Freshsales17

Delete a Sales Activity

Action

In MakeDeletes a specific Freshsales activity.

Removes a logged sales activity from Freshsales, which keeps activity reports honest when entries were created twice or by mistake.

When to use it
when a sync from a field or event tool pushed duplicates and a manager asked for them to go.
Watch out
activity counts in reports change as soon as the entry is gone, warn whoever reads them.
Freshsales18

Delete a Task

Action

In MakeDeletes a specific Task.

Drops a task from Freshsales once it has lost its purpose, for instance when the deal it prepared was closed in the meantime.

When to use it
when a task created by automation should vanish because the customer already answered through another channel.
Watch out
Update a Task marking it done keeps a trace; deleting leaves none.
Freshsales19

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Opens the whole Freshsales API to your scenario with the connection you already set up, so a need the listed modules miss is still within reach.

When to use it
when you need an object or an operation that none of the 56 ready modules offers.
Watch out
you write the request yourself, so keep the Freshsales API documentation open while you set it up.
Freshsales20

Update a Contact

Action

In MakeUpdates information of specific contact.

Changes the details of an existing Freshsales contact from fresh data elsewhere, so a new phone number or job title reaches the CRM without a rep typing it.

When to use it
when a customer edits their profile in your app or your billing tool.
Watch out
find the contact ID first with Search Contacts, the module updates one record by its ID.
Freshsales21

Update a Deal

Action

In MakeUpdates information of a specific deal.

Moves an opportunity forward in Freshsales from what happens outside it, a signed contract, a paid invoice, a rejected quote, so the pipeline mirrors the business.

When to use it
when an e-signature or payment tool confirms the outcome of a deal.
Watch out
take the deal ID from View a Deal or Search Deals, never from a name typed by hand.
Freshsales22

Update a Lead

Action

In MakeUpdates information of a specific lead.

Enriches or corrects a lead already in Freshsales, so the rep calling tomorrow sees the latest information, not last month's.

When to use it
when a second form, a webinar signup or an enrichment tool adds information about a known prospect.
Watch out
pair it with Search Leads, which may return several matches, and keep the right one before updating.
Freshsales23

Update an Account

Action

In MakeUpdates information of specific account.

Keeps a Freshsales company record in step with your other systems, so address, plan or owner changes do not live in one tool only.

When to use it
when a client upgrades their subscription in your billing tool and account managers should see it.
Watch out
use the account ID from Search Accounts or View an Account, never a name typed by hand.
Freshsales24

Update an Appointment

Action

In MakeUpdates information of specific appointment.

Moves or edits a meeting in Freshsales when the booking changes elsewhere, so the rep prepares for the meeting as it now stands.

When to use it
when a prospect reschedules through an external booking page.
Watch out
the scenario needs the Freshsales appointment ID; store it when the appointment is first created.
Freshsales25

Update a Note

Action

In MakeUpdates a specific note.

Rewrites the text of an existing Freshsales note, which lets one note track a situation that evolves instead of stacking a new note at each change.

When to use it
for a status summary on a deal that another tool refreshes, like an order or a support case.
Watch out
you need the note ID, so keep it from the Create a Note output.
Freshsales26

Update a Sales Activity

Action

In MakeUpdates information of a specific Freshsales activity.

Corrects or completes a sales activity already logged in Freshsales, so outcomes and notes added after the fact still land on the same entry.

When to use it
when a field visit is logged first and its report arrives later from a mobile form.
Watch out
keep the activity ID from Create a Sales Activity, the update targets one entry only.
Freshsales27

Update a Task

Action

In MakeUpdates a specific task.

Changes an existing Freshsales task based on what happens outside the CRM, so reps are not chasing tasks that are already handled.

When to use it
when the customer replies by email or pays, and the pending callback task can be closed.
Watch out
it needs the task ID, so keep it from Create a Task or from the Watch New Tasks bundle.
Freshsales28

Upload a File

Action

In MakeUploads and attach a file to a lead, contact, sales account or a deal.

Attaches a document to a lead, contact, sales account or deal in Freshsales, so contracts, quotes and briefs sit on the record the rep opens.

When to use it
when a signed PDF comes back from your e-signature tool or a quote is generated elsewhere.
Watch out
on the Free plan, Make handles files up to 5 MB, keep that in mind for scanned contracts.
Freshsales29

View a Contact

Action

In MakeViews details of a specific contact.

Fetches the full details of one Freshsales contact by its ID, so later modules can use fields the trigger or search did not carry.

When to use it
when an email or invoice needs the contact's full record and you only have the ID from an earlier step.
Watch out
it reads a single contact; for several, Search Contacts or List All Contacts fit better.
Freshsales30

View a Deal

Action

In MakeViews details of a specific deal.

Reads everything Freshsales holds on one opportunity, so your scenario has the full record in hand before it decides what to do next.

When to use it
when an earlier step gives you only the deal ID and the next module needs the whole deal.
Watch out
each view counts as one operation, so avoid calling it when the trigger already brings the data.
Freshsales31

View a Lead

Action

In MakeViews details of a specific lead.

Pulls the complete profile of a single Freshsales lead, handy to check its details before routing the prospect to the right person.

When to use it
when another tool sends a lead ID and your scenario must decide what to do based on its details.
Watch out
it reads one lead; to scan many, List All Leads or Search Leads fit better.
Freshsales32

View an Account

Action

In MakeViews details of a specific account.

Retrieves one Freshsales account with its details, so an invoice, a contract or a welcome pack uses the company data sales keeps up to date.

When to use it
when a new deal arrives and the billing step needs the company details sales keeps on the account.
Watch out
you need the account ID; Search Accounts gets it from a company name.
Freshsales33

View an Appointment

Action

In MakeViews details of a specific appointment.

Reads the details of one Freshsales meeting, so a reminder or a prep message draws on the meeting as it is stored in the CRM.

When to use it
when a scenario receives an appointment ID and has to build a message around the meeting.
Watch out
keep the appointment ID from Create an Appointment or from the trigger bundle, it is the only way to target one meeting.
Freshsales34

View a Sales Activity

Action

In MakeViews details of a specific Freshsales activity.

Opens a single Freshsales sales activity and hands its details to the next module, which is useful when a report or message needs the full entry.

When to use it
after Watch New Sales Activities, when you want to enrich the activity before copying it to a sheet.
Watch out
it works on one activity ID at a time.
Freshsales35

View a Task

Action

In MakeViews details of a specific task.

Looks up one Freshsales task by its ID, so your scenario can check whether it is still open before sending a reminder or escalating it.

When to use it
in a follow-up scenario that should nudge a manager only when the task is still pending.
Watch out
the answer reflects the task at that moment, a rep may close it a minute later.
Freshsales36

List All Accounts

Search

In MakeLists all accounts on your Freshsales account.

Returns every account in your Freshsales, one bundle per company, which is the starting point for exports, audits and bulk syncs.

When to use it
when you copy the full account list to a spreadsheet or a data warehouse.
Watch out
each account becomes a bundle and every following module runs once per bundle, so the operation count grows with your database.
Freshsales37

List All Appointments

Search

In MakeLists all appointments on your Freshsales account.

Brings back all appointments stored in Freshsales, one per bundle, so you can rebuild a meeting overview or sync it into another calendar tool.

When to use it
when a manager wants a full meeting report outside the CRM.
Watch out
every appointment becomes a bundle, so add a filter before the next module if you only need some of them.
Freshsales38

List All Contacts

Search

In MakeLists all contacts on your Freshsales account.

Outputs the complete contact base of your Freshsales account, one bundle per person, useful for a first sync or a cleanup pass.

When to use it
when you set up a new mailing or support tool and it needs every existing contact once.
Watch out
for a single person, Search Contacts avoids spending an operation on every record.
Freshsales39

List All Deals

Search

In MakeLists all deals on your Freshsales account.

Delivers every Freshsales deal to your scenario, one bundle each, so forecasts and pipeline reports can be rebuilt in the tool finance actually reads.

When to use it
when leadership wants the pipeline in a spreadsheet or dashboard outside Freshsales.
Watch out
run it with Run once first and look at the number of bundles before switching the scenario on.
Freshsales41

List All Leads

Search

In MakeLists all leads on your Freshsales account.

You get every lead stored in your Freshsales account, handed to the next module one bundle at a time (a bundle is a single item passing between modules, here one lead).

When to use it
when a sales manager wants the whole lead base copied into a spreadsheet or reviewed in one pass, rather than chasing a single person.
Watch out
each lead that comes out makes the following modules run once more, and every run is an operation counted on your Make plan.
Freshsales42

List All Sales Activities

Search

In MakeLists all Freshsales activities on your account.

This module pulls all the sales activities logged in Freshsales, each one travelling into another tool as its own bundle.

When to use it
when a team lead needs the full activity history in a report, instead of only the new ones that Watch New Sales Activities catches.
Watch out
a long history means many bundles, and each one triggers the next modules again, so test it with Run once before activating the scenario.
Freshsales43

List All Tasks

Search

In MakeLists all tasks on your Freshsales account.

Every task in your Freshsales account comes back here, which lets a scenario review the complete to-do list of the sales team.

When to use it
when an ops manager wants to push all open tasks into a project board or a shared sheet after an import or a cleanup.
Watch out
Watch New Tasks only picks up new tasks; this list is the module that reaches the ones already there, so expect a large first run.
Freshsales44

Search Accounts

Search

In MakeSearches through your Freshsales account for match.

Here you find the matching company records (accounts) in Freshsales, so the scenario can reuse an existing account instead of guessing.

When to use it
before Create an Account when a web form sends a company name and you want to avoid a duplicate record in the CRM.
Watch out
a search can return zero, one or several accounts; plan what the next modules should do in each case before you activate the scenario.
Freshsales45

Search Contacts

Search

In MakeSearches through your Freshsales account for match.

With this search, a scenario checks whether a person already exists as a contact in Freshsales and gets back the matching records to work with.

When to use it
in a support or billing flow: an email lands in another app and you need the contact behind it before calling Update a Contact.
Watch out
when nobody matches, no bundle comes out and the modules placed after it do not run, which is easy to miss while testing with Run once.
Freshsales46

Search Deals

Search

In MakeSearches through your Freshsales account for match.

Deals that match your criteria come back from this search, ready to be updated, reported on or linked to something happening elsewhere.

When to use it
when an invoice gets paid in your billing tool and you want to locate the related deal in Freshsales before moving it forward with Update a Deal.
Watch out
several deals may match the same query; if only one should be touched, keep the first result or refine the query, otherwise every match gets updated.
Freshsales47

Search Leads

Search

In MakeSearches through your Freshsales account for match.

The module looks through your Freshsales leads and returns those that match, so a new signup can be compared with people you already know.

When to use it
at the start of a lead capture flow: search first, then run Create a Lead only when the result is empty, or Convert a Lead when the prospect is ready.
Watch out
Convert a Lead moves a lead to the contact side, so someone already converted is likely to be missing here; pair it with Search Contacts when that matters.
Freshsales48

Search Users

Search

In MakeSearches through your Freshsales account for match.

Instead of prospects, this one finds the people on your own Freshsales team, the users, so a scenario can assign work to the right salesperson.

When to use it
when a task or appointment should go to a named rep: look the user up first, then pass the result to Create a Task.
Watch out
a user is a teammate with a Freshsales login, not a customer; searching here for a client name returns nothing.
Need help

Need help automating Freshsales with Make?

A person reads every message.

FAQ

Freshsales and Make: common questions

01Is the Freshsales Make integration free?
Yes, on the Make side. Freshsales is a standard app, available from the Free plan. That plan allows 2 active scenarios, a shortest interval of 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) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. You still need an active Freshsales CRM account on your side, with its own subscription.
02What do you need to connect Freshsales to Make?
An active Freshsales CRM account and its API key. In Freshsales, open Settings from the Profile icon, go to the API SETTINGS tab, complete the captcha and copy the key shown in Your API key. In Make, add any Freshsales module, click Create a connection, optionally name it, and paste the credentials. The connection is then shared by every Freshsales module in your scenarios. For the instant Watch New Events trigger, click Create a webhook first, then Create a connection.
03Do Freshsales triggers in Make fire in real time?
Only one does. Watch New Events is instant: a Freshsales Workflow calls Make through a webhook as soon as its event occurs. The seven other triggers, including Watch New Leads, Watch New Deals and Watch New Contacts, are scheduled. Make checks Freshsales on the scenario's schedule, every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. If a delay of a few minutes is a problem, build the flow around Watch New Events.
04What if a Freshsales module is missing in Make?
Use Make an API Call. It reuses your Freshsales connection and can reach any endpoint of the Freshsales API, so objects or operations that the 56 ready modules do not cover remain available. You write the request yourself, which means reading the Freshsales API documentation for the path and the expected body. If the gap is about speed rather than coverage, the instant Watch New Events trigger, fed by a Freshsales Workflow, is the other lever. When a run fails, the Make troubleshooting guide is a good first stop, then the bundles shown after Run once.
05Should you use Make or n8n for Freshsales?
It depends on your criteria rather than on a winner. On Make, Freshsales comes with 56 modules covering leads, contacts, deals, accounts, appointments, tasks, notes, sales activities and files, plus Make an API Call for the rest, and a Free plan to test with 2 active scenarios. The same app often has an n8n node too, so compare the list of operations each side offers for your use case, and look at which editor your team already knows. The comparison page linked above sets out both tools side by side.