Resources · Make integration

Freshservice Make integrationAutomate Freshservice with Make.

Can Make keep your service desk moving without a single line of code? The Freshservice Make integration gives you 47 modules: 7 triggers, 32 actions and 8 searches. This guide is for IT and ops teams who know Freshservice well but are new to Make.

Try the Freshservice integration on MakeSee the 47 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can a Freshservice Make integration do for your team?

A Freshservice Make integration links your service desk to the rest of your tools without code. In Make you build a scenario, the automation itself, made of bricks called modules. It watches Freshservice for new or updated records, then creates, updates or looks up tickets, requesters, changes, problems, releases, tasks and time entries.

An onboarding ticket for every new requester. Watch Requesters notices a person added to Freshservice, and Create a Ticket opens the setup request for them, so a new starter never waits on someone remembering.

One clean record per person. When your HR tool adds a hire, Search Requesters checks whether that person already exists. Create a Requester or Update a Requester then keeps a single profile instead of two.

Changes visible outside the service desk. Watch Changes and Watch Release send each creation or update to a shared sheet or a team channel, for the people who never open Freshservice.

What the app does not do: all 7 triggers are scheduled, so Make checks Freshservice on the scenario's schedule rather than hearing about events the moment they happen. The Make documentation for this app also says it is AI-generated and may contain mistakes, so verify anything critical against Freshservice itself. When the listed modules fall short, Make an API Call reaches the rest of the API with the same connection.

Freshservice also has an n8n node, covered on the Freshservice n8n integration page, and n8n vs Make sets the two tools side by side. Starting from zero in the editor? The Make training covers the basics.

Connect

How do you connect Freshservice to Make?

  1. 01

    Copy your API key in Freshservice

    Make signs in to Freshservice with an API key, so grab it first. In the Freshservice portal, click your profile picture in the top right corner, open Profile settings and copy the API key shown below the Delegate Approvals section.

  2. 02

    Add a module and create the connection

    In a Make scenario, add any Freshservice module and click Create a connection. A connection is your Freshservice account linked to Make once, then reused by every Freshservice module. The Connection name field is optional but handy later.

  3. 03

    Paste the key and save

    Enter the credentials you copied from Freshservice, or follow the instructions Make shows on screen. Once saved, the connection appears in the module, and Make can list the records it is able to read from your account.

First scenario

Your first scenario: an onboarding ticket for each new requester

GoalWhen a requester is created or updated in Freshservice, Make opens a ticket for that person.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Picture the scenario as a recipe and each module as one step of it.

  2. 02

    Add Watch Requesters

    Search for Freshservice, pick Watch Requesters and choose the connection you just made. This trigger is scheduled and also returns edited requesters, so a profile update can open a second ticket. Test with one requester first.

  3. 03

    Add Create a Ticket

    Click the + on the right of the trigger and add Create a Ticket. Map the requester data coming from Watch Requesters into the ticket so the request lands under the right person.

  4. 04

    Test with Run once

    Add a test requester in Freshservice, then click Run once. Each module shows the bundles it received (a bundle is one item passing through, here one requester), so you can check the ticket before going live.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, also the minimum on the Free plan; paid plans go down to 1 minute. Then switch the scenario on.

Triggers

What can start a Freshservice scenario?

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

Freshservice1Watch Changes

Watch Changes

Scheduled trigger

In Make“Triggers if a change is created or updated.”

Brings every change created or updated in Freshservice into Make, one bundle per change. A change is a planned piece of IT work, such as a server upgrade, that someone approves before it happens. It keeps people who never open the service desk in the loop.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
a planned change should be posted to a team channel or copied to a planning sheet as soon as the next check sees it.
Watch out
updates count too, so a change edited several times can come through more than once. Plan for that in the next module, for instance by looking the record up before you create anything from it.
Freshservice2Watch Problems

Watch Problems

Scheduled trigger

In Make“Triggers if a problem is created or updated.”

Hands your scenario each problem record that someone opens or edits in Freshservice. A problem is the record that hunts for the shared cause behind incidents that keep coming back. It suits teams that want root-cause work to be visible beyond the agents who handle it.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new problem shows up at the next run, not instantly.
When to use it
you want engineering or a vendor to hear about a new problem through their own tool, like a chat channel or a shared tracker.
Watch out
an edit to an existing problem also triggers a run. If you only want brand new problems, compare what arrives with what you already sent.
Freshservice3Watch Release

Watch Release

Scheduled trigger

In Make“Triggers if a release is created or updated.”

Spots releases as they are created or modified in Freshservice and passes each one to the rest of the scenario. A release is a rollout: a batch of changes delivered together. Note the singular in the name: that is how Make labels this module.

How it fires
scheduled. Make checks the app on the scenario's schedule and processes what it finds at that moment.
When to use it
your support team, or the customers they serve, need a heads-up about upcoming rollouts without being given access to Freshservice.
Watch out
a release that gets reworked several times will pass through several times. Keep the message you send short and factual so repeats do not confuse anyone.
Freshservice4Watch Requesters

Watch Requesters

Scheduled trigger

In Make“Triggers if a requester is created or updated.”

Returns each requester (the person who asks IT for help) added or changed in Freshservice, which makes it the natural starting point for onboarding and directory syncs.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, 1 minute at best on a paid plan.
When to use it
a new person in Freshservice should get a welcome ticket, a record in your HR tool or a line in a shared contact sheet.
Watch out
if a later module in the same scenario runs Update a Requester, that update can wake the trigger again on the next check. Keep the watching and the editing in separate scenarios.
Freshservice5Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers if a task is created or updated.”

Picks up tasks that are created or updated in Freshservice, so the small to-dos inside larger records stop living only in the service desk.

How it fires
scheduled. Make checks the app on the scenario's schedule instead of being pinged by Freshservice.
When to use it
technicians work from a personal to-do app or a team board and want their Freshservice tasks copied there at each check.
Watch out
a task that is reassigned or edited counts as an update and comes back through the scenario. Decide early whether your next module should create a new item or refresh the one it made before.
Freshservice6Watch Tickets

Watch Tickets

Scheduled trigger

In Make“Triggers if a ticket is created or updated.”

Feeds your scenario with tickets that are opened or changed in Freshservice. It is the trigger most service desk automations start from.

How it fires
scheduled. Make checks the app on the scenario's schedule; it is not real time, so plan on a short delay between the ticket and the reaction.
When to use it
a high-impact ticket should reach a manager's chat, a customer record in your CRM, or a reporting sheet without anyone forwarding it.
Watch out
avoid Create a Ticket or Update a Ticket in the same scenario, since the tickets they touch can be picked up again at the next check.
Freshservice7Watch Time Entries

Watch Time Entries

Scheduled trigger

In Make“Triggers if a time entry is created or updated.”

Sends Make each time entry logged or corrected in Freshservice. Finance and account managers get hours without asking the service desk for an export.

How it fires
scheduled. Make checks the app on the scenario's schedule and gathers the entries it finds at that run.
When to use it
billable hours logged by technicians need to land in an invoicing tool or a client timesheet.
Watch out
a corrected entry comes through as an update, not as a new one. If you add hours up downstream, replace the old value rather than stacking both, or your totals will drift.
Modules

Everything the Freshservice app can do in Make

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

Freshservice1

Create a Change

Action

In Make“Creates a new change.”

Opens a new change record in Freshservice straight from your scenario, so a request that starts in another tool enters the change process without being retyped.

When to use it
an approved request in a form or a vendor maintenance notice should become a change your approvers can review.
Watch out
every run creates a fresh record, so the same input processed twice gives you two changes. Run Search Changes first when duplicates are possible.
Freshservice2

Create a Problem

Action

In Make“Creates a new problem.”

Logs a problem in Freshservice, the record your team uses to chase the cause behind repeated incidents, from whatever source spotted the pattern.

When to use it
a monitoring alert or a spreadsheet of recurring issues flags the same fault again and you want it tracked instead of lost in a chat thread.
Watch out
the app has List Problems but no search module for problems, so checking for an existing one means reading the full list in the scenario first.
Freshservice3

Create a Release

Action

In Make“Creates a new release.”

Adds a release to Freshservice, giving a rollout its own record as soon as it is planned somewhere else.

When to use it
a deployment gets scheduled in your development tool and the service desk should see the matching release without copying it across.
Watch out
the module does not look for an existing release before writing. If the same deployment can reach the scenario twice, check List Releases before creating anything.
Freshservice4

Create a Requester

Action

In Make“Creates a new requester.”

Registers a person as a requester in Freshservice, ready to raise tickets and to be found by your agents when they call.

When to use it
a new employee appears in your HR tool, or a client contact is added to your CRM, and they need a service desk profile before their first request.
Watch out
place Search Requesters right before it. Two profiles for the same person leave agents guessing which one holds the history.
Freshservice5

Create a Task

Action

In Make“Creates a new task on one of 4 modules.”

Adds a task in Freshservice. According to the official description, it works on one of 4 Freshservice modules (parts of Freshservice, not bricks of your scenario), so decide where the task belongs before you build.

When to use it
a record needs a concrete follow-up for a technician, such as preparing equipment before a new starter arrives.
Watch out
the description does not name those 4 modules. Look at the options Make lists in the module once your connection is set, before mapping anything.
Freshservice6

Create a Ticket

Action

In Make“Creates a new ticket.”

Raises a ticket in Freshservice from any event your scenario catches: a form entry, an alert from another tool, a row added to a sheet.

When to use it
requests arrive outside the portal and you want them in the same queue as everything else, with nobody copying them by hand.
Watch out
if Watch Tickets starts the same scenario, a ticket you create can be picked up again on the next check. Keep the two in separate scenarios.
Freshservice7

Create a Time Entry

Action

In Make“Creates a new time entry on one of 4 modules.”

Records time spent in Freshservice, logged on one of the 4 modules the official description mentions, so the hours sit next to the work.

When to use it
your technicians track hours in a separate timesheet app and you want the same hours visible in Freshservice for reporting.
Watch out
if technicians also use Start/Stop Timer on the same record, hours can end up counted twice. Choose one way of logging time per team.
Freshservice8

Deactivate a Requester

Action

In Make“Deactivates a chosen requester.”

Deactivates the requester you point it to, the natural offboarding step for someone who should no longer raise tickets.

When to use it
your HR tool marks an employee as gone, and you want the matching Freshservice requester deactivated without a manual pass.
Watch out
a separate module, Forget a Requester, exists too, and the Make documentation does not explain how they differ. Test on a dummy requester first and look at what happens to the profile.
Freshservice9

Delete a Change

Action

In Make“Deletes a chosen change.”

Removes a change from Freshservice. Nothing in Make brings it back afterwards, so this module deserves a careful setup.

When to use it
test changes created while you were building a scenario, or duplicates left by an earlier run, need clearing out.
Watch out
map the change from a previous module instead of typing it, and check with Run once that the bundle is the record you meant before you switch the scenario on.
Freshservice10

Delete a Problem

Action

In Make“Deletes a chosen problem.”

Erases a problem record from Freshservice for good, which keeps your problem list focused on causes that are still open.

When to use it
two problems were logged for the same root cause, and the team decided to keep only one of them.
Watch out
put Get a Problem just before it. When you test, read that bundle and confirm it is the problem you expect, because a wrong mapping deletes the wrong record.
Freshservice11

Delete a Release

Action

In Make“Deletes a chosen release.”

Takes a release out of Freshservice completely, rather than leaving a record nobody will act on.

When to use it
a rollout was entered by mistake, or a scenario test created a release that should never have existed.
Watch out
once deleted, the record and its history are gone. If people may want to see what was planned, keep it and change it with Update a Release instead of erasing it.
Freshservice12

Delete a Task

Action

In Make“Deletes a chosen task from one of 4 modules.”

Removes a task from one of the 4 modules named in the official description, cleaning up to-dos that no longer make sense.

When to use it
a parent request was cancelled in another tool and its pending tasks in Freshservice should disappear with it.
Watch out
you must point at the right parent as well as the right task. Get a Task in front of it lets you confirm both in the test run.
Freshservice13

Delete a Ticket

Action

In Make“Deletes a chosen ticket.”

Deletes a ticket from Freshservice. It is the most drastic ticket module in the app, and the one to set up last.

When to use it
spam or test tickets keep landing in the queue and you want a scenario to clear them once they are clearly identified.
Watch out
there is no undo. Put a strict condition upstream, such as a match found by Search Tickets, and never feed it the raw output of Watch Tickets.
Freshservice14

Delete a Time Entry

Action

In Make“Deletes a chosen time entry from one of 4 modules.”

Removes a time entry from one of the 4 modules the description refers to, so reports stop showing hours that were never worked.

When to use it
a timesheet app cancels a logged session and the matching Freshservice entry should go too.
Watch out
once hours are billed, deleting them in Freshservice will not update an invoice already sent. Clean up before the numbers leave the service desk.
Freshservice15

Forget a Requester

Action

In Make“Forgets a chosen requester.”

Forgets the requester you choose. The Make documentation does not say what Freshservice removes, or how it differs from Deactivate a Requester.

When to use it
only after checking in the Freshservice documentation what forgetting a requester does, and confirming it is what you need.
Watch out
treat it as irreversible until proven otherwise. Try it on a test requester before pointing it at real people.
Freshservice16

Get a Change

Action

In Make“Retrieves a single change.”

Fetches one change you already know, with its full details, so later modules can use them.

When to use it
another tool only passes you a reference to a change, and you need the rest of the record before writing a summary or notifying approvers.
Watch out
Get a Change reads one record, not several. To find changes matching a condition, reach for Search Changes, which can return many bundles at once.
Freshservice17

Get an Asset

Action

In Make“Retrieves a single asset.”

Retrieves a single asset from your Freshservice inventory, such as a laptop or a license, with its details ready to map.

When to use it
a ticket mentions a device and you want its information in the reply, the purchase request or the report the scenario builds.
Watch out
the app can read assets but has no module to create or update them. For those, Make an API Call is the way through.
Freshservice18

Get a Problem

Action

In Make“Retrieves a single problem.”

Loads one problem record in full, which is useful when an earlier step only gave you its reference.

When to use it
a review sheet or a chat message needs the problem's latest details before the scenario writes anything.
Watch out
if you do not know which problem you want, this is the wrong module. List Problems returns all of them and lets later modules pick.
Freshservice19

Get a Release

Action

In Make“Retrieves a single release.”

Reads a single release from Freshservice and exposes its details to the rest of the scenario.

When to use it
you announce a rollout to customers and want the text built from the release record itself, not from memory.
Watch out
the release must exist when the module runs. Map it from a previous module, like Watch Release or List Releases, rather than hard-coding a reference that may go stale.
Freshservice20

Get a Requester

Action

In Make“Retrieves a single requester.”

Pulls up one requester's profile, so the scenario knows who it is dealing with before acting.

When to use it
a ticket arrives and you want the requester's details in the chat alert or CRM note the scenario sends next.
Watch out
it needs to know which requester to read. If all you have is a name or an email from another tool, start with Search Requesters instead.
Freshservice21

Get a Task

Action

In Make“Retrieves a single task on one of 4 modules.”

Retrieves one task, attached to one of the 4 modules listed in the official description, with everything recorded on it.

When to use it
before closing or deleting a task, you want to confirm its current state in a test run.
Watch out
both the task and its parent have to be identified correctly. A task pulled from the wrong parent returns nothing useful, so map both from earlier modules.
Freshservice22

Get a Ticket

Action

In Make“Retrieves a single ticket.”

Returns the full content of one ticket, handy when an email, a chat command or another app only hands you its reference.

When to use it
a manager types a ticket reference into a chat tool and the scenario replies with its details.
Watch out
one run of this module equals one operation per bundle. If you call it for every ticket a search returns, your operation count grows with the list.
Freshservice23

Get a Time Entry

Action

In Make“Retrieves a single time entry on one of 4 modules.”

Reads one time entry from one of the 4 modules in the description, useful for checking hours before they are billed or reported.

When to use it
an invoicing scenario needs the exact entry a technician logged, not a total.
Watch out
to pull every entry for a record, List Time Entries is the right module; Get a Time Entry expects one precise entry.
Freshservice24

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Freshservice API with the connection you already set up. It is the way out when none of the listed modules does what you need.

When to use it
you need an operation the list does not cover, such as creating or updating an asset.
Watch out
here you work with the API's own requests and answers, so keep the Freshservice API documentation open while you build.
Freshservice25

Start/Stop Timer

Action

In Make“Starts or stops a timer on one of 4 modules.”

Starts or stops a timer on one of the 4 modules the description mentions, so time tracking follows events instead of relying on someone clicking.

When to use it
a technician picks up a request in another tool and you want the Freshservice timer running at the same moment.
Watch out
a scenario that starts timers needs a matching way to stop them. Otherwise timers can keep running and inflate the hours on the record.
Freshservice26

Update a Change

Action

In Make“Updates a change.”

Edits an existing change in Freshservice, keeping the record in step with what happens elsewhere.

When to use it
a deployment tool reports success or failure and the matching change in Freshservice should reflect it.
Watch out
an update wakes Watch Changes again. Keeping Watch Changes and Update a Change in one scenario can make it process its own edits over and over.
Freshservice27

Update a Problem

Action

In Make“Updates a problem.”

Changes a problem already logged in Freshservice, for instance to record what an investigation found in another tool.

When to use it
engineering closes the issue in their tracker and you want the Freshservice problem brought up to date without asking anyone.
Watch out
you need the right problem first. Pair it with Get a Problem or List Problems, then check in Run once that the correct record is edited.
Freshservice28

Update a Release

Action

In Make“Updates a release.”

Modifies an existing release, which keeps your rollout plan accurate when dates or scope shift somewhere else.

When to use it
the project tool moves a delivery and the Freshservice release should follow instead of showing an outdated plan.
Watch out
Watch Release sees your edit as a new update. If both live in one scenario, one edit can trigger another run and loop.
Freshservice29

Update a Requester

Action

In Make“Updates a requester.”

Refreshes a requester's profile in Freshservice so agents see current information when that person writes in.

When to use it
someone changes team or job title in your HR tool and Freshservice should know without a ticket to IT.
Watch out
find the person with Search Requesters first. If no one matches, route the bundle to Create a Requester rather than letting the update fail.
Freshservice30

Update a Task

Action

In Make“Updates a task on one of 4 modules.”

Edits a task on one of the 4 modules from the description, so its state mirrors the tool where the work actually happens.

When to use it
a technician ticks off an item in their board and you want the Freshservice task updated to match.
Watch out
Watch Tasks will catch this edit on its next check. Keep that trigger in another scenario to avoid a loop.
Freshservice31

Update a Ticket

Action

In Make“Updates a ticket.”

Changes a ticket that already exists, so information arriving from other tools ends up on the record agents actually read.

When to use it
a customer replies through another channel, or a supplier confirms a fix, and the ticket should reflect it straight away.
Watch out
a scenario that starts with Watch Tickets and ends with Update a Ticket can pick up its own changes at the next check and run again.
Freshservice32

Update a Time Entry

Action

In Make“Updates a time entry on one of 4 modules.”

Corrects a time entry on one of the 4 modules the description names, without deleting and re-creating it.

When to use it
the timesheet app adjusts a session after review and the Freshservice entry should carry the corrected hours.
Watch out
Watch Time Entries treats your correction as an update. Anything downstream that adds hours must replace the old value, not add the new one on top.
Freshservice33

List Problems

Search

In Make“Retrieves a list of all problems.”

Returns all the problems in Freshservice, one bundle per problem, for a full picture instead of a single record.

When to use it
you build a status sheet of open investigations, or you check whether a similar problem exists before creating one.
Watch out
every problem becomes a bundle, and each module after it runs once per bundle. A long list means many operations on your plan.
Freshservice34

List Releases

Search

In Make“Retrieves a list of all releases.”

Pulls every release from Freshservice into the scenario, one bundle each, ready to sort or send.

When to use it
a shared rollout calendar or dashboard needs all releases, not just the ones that changed recently.
Watch out
this module has no search condition in its name, so expect the whole list. Narrow things down in the modules that follow, and watch your operation count.
Freshservice35

List Tasks

Search

In Make“Retrives a list of all tasks from one of 4 modules.”

Gathers all tasks from one of the 4 modules the description refers to, so you can review them together.

When to use it
before closing a parent record, you want to see whether any task under it is still open.
Watch out
the result can be zero, one or many bundles. When it is empty, the modules after it simply do not run, which surprises people during a first test.
Freshservice36

List Time Entries

Search

In Make“Retrieves a list of all time entries from one of 4 modules.”

Collects all time entries from one of the 4 modules in the description, the raw material for any hours report.

When to use it
a client report needs every entry logged on a record, not a single one fetched by reference.
Watch out
each entry is its own bundle. To get a total you will need to add them up in the scenario, and every bundle costs operations.
Freshservice37

Search Assets

Search

In Make“Searches for assets or lists them all.”

Looks for assets in Freshservice, or lists them all when you leave the search open. It is the inventory lookup of the app.

When to use it
a new starter's ticket should mention which device is waiting for them, or an audit sheet needs the full asset list.
Watch out
an open search returns every asset as a separate bundle. Search precisely when you only need one device.
Freshservice38

Search Changes

Search

In Make“Searches for changes or lists them all.”

Finds changes matching what you ask for, or returns all of them when you do not filter.

When to use it
before Create a Change, you want to know whether the same request already exists, to avoid a duplicate for your approvers.
Watch out
zero results is a normal outcome, not an error. Decide what the scenario should do in that case, usually create the change.
Freshservice39

Search Requesters

Search

In Make“Searches for requesters or lists them all.”

Checks your Freshservice requesters for a person, or lists everyone if the search is left open.

When to use it
a contact comes from a form or an HR tool, and the scenario must decide between Update a Requester and Create a Requester.
Watch out
more than one match can come back. Make then sends each through the next modules, so one input could update several people.
Freshservice40

Search Tickets

Search

In Make“Searches for tickets or lists them all.”

Searches the ticket queue, or lists every ticket, and returns what it finds as separate bundles.

When to use it
a customer writes in through another channel and you want their existing ticket found before a new one is opened.
Watch out
searching without a condition can return the entire queue. Each ticket then runs through the next modules and costs operations.
Need help

Need help automating Freshservice with Make?

A person reads every message.

FAQ

Freshservice and Make: common questions

01Is the Freshservice Make integration free?
Yes, as far as Make is concerned. Freshservice is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module per bundle. Your Freshservice subscription is a separate matter: check the Freshservice pricing page.
02What do you need to connect Freshservice to Make?
An active Freshservice account and its API key. To find the key, click your profile picture at the top right of the Freshservice portal, open Profile settings, and copy the API key shown below the Delegate Approvals section. Then add any Freshservice module in Make, click Create a connection, give it a name if you like, and paste the credentials. The same connection serves all 47 Freshservice modules afterwards, so you only do this once per account.
03Do Freshservice triggers in Make react in real time?
No. All 7 Freshservice triggers are scheduled: Make checks Freshservice on the scenario's schedule instead of receiving a webhook. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Each trigger reacts to records that are created or updated, so an edited ticket or requester can come through again, and your next modules should be ready for that.
04What if the Freshservice module you need is missing?
Use Make an API Call. It reaches any endpoint of the Freshservice API with the connection you already have, which covers gaps such as creating or updating assets, since the app only reads and searches them. You then work with the API's own format, so keep the Freshservice API documentation nearby. Also keep in mind that Make's documentation for this app is AI-generated and may contain mistakes, so confirm important details with Freshservice.
05Should you automate Freshservice with Make or n8n?
It depends on your case. Freshservice exists on both platforms: in Make as an app with 47 modules, and in n8n as a node with its own guide on this site. Start from the records you need to touch, check that the tool you lean toward covers them, and favor the one where your other automations already run so you manage everything in one place. The n8n vs Make comparison on this site goes through the differences between the two tools in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations