Resources · Make integration

Microsoft 365 Excel Make integrationAutomate Microsoft 365 Excel with Make.

Can Make keep your Excel workbooks filled without any copy and paste? Yes. The Microsoft 365 Excel Make integration gives you 22 modules, 3 of them triggers. This guide shows ops and finance teams how to connect an account and ship a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft 365 Excel Make integration do?

The Microsoft 365 Excel Make integration links your workbooks to Make, a no-code automation tool. You build a scenario, the automation itself, out of modules: small bricks that each watch, add, update or read something in Excel. Data from your other apps lands in the right table, and fresh Excel rows can start work elsewhere.

A sales log that fills itself. When a deal closes in your CRM, Add a Table Row writes it into the sales table, so the sheet your manager opens is already current.

A reaction to every new line. Watch Worksheet Rows spots rows your team types in by hand, and the next module can send an email or open a task in another tool.

Figures pulled when you need them. Retrieve Data reads a range you define, say the totals block of a budget, and hands the values to a report or a message.

What it does not do: every trigger here is scheduled, so Make checks Excel on the scenario's schedule instead of hearing about changes as they happen. For anything the 22 modules miss, Make an API Call reaches the rest of the API with the same connection. The same app often has an n8n node too, and the n8n vs Make page helps you choose. New to the editor? Make training covers the basics, and the Airtable Make integration shows the same logic on another data tool.

Connect

How do you connect Microsoft 365 Excel to Make?

  1. 01

    Add an Excel module

    In your scenario, click the +, search for Microsoft 365 Excel and pick any module, trigger or action. Then click Create a connection. A connection is your Microsoft account linked to Make once and reused afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when a work account and a personal one sit side by side. Make then opens the app's authorization page: sign in with the account that owns your workbooks and allow access.

  3. 03

    Save and pick your files

    Click Save. Back in the module, Make now lists the workbooks, worksheets and tables it can read, so you choose from a menu instead of typing anything. Every other Excel module reuses this same connection.

First scenario

Your first scenario with Microsoft 365 Excel

GoalWhen a new workbook is created in Microsoft 365 Excel, Make adds a worksheet to it so every file starts with the same tab.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the large +. That spot holds the first module, the one that starts everything.

  2. 02

    Set up Watch Workbooks

    Search for Microsoft 365 Excel, pick Watch Workbooks and select your connection. Make shows what it can read in your account; fill in the fields it asks for.

  3. 03

    Add the worksheet module

    Click the + to the right of the trigger and add Add a Worksheet. Map the workbook coming from the first module, so each new file receives its own tab.

  4. 04

    Test with Run once

    Create a test workbook, then click Run once. Open the bubble above each module to see the bundle it received, here one workbook, one item passed from module to module.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Triggers

What starts a Microsoft 365 Excel scenario

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

Microsoft 365 Excel1Watch Table Rows

Watch Table Rows

Scheduled trigger

In MakeTriggers when a new row is added to a table.

Every row added to an Excel table turns into a bundle, one item handed to the rest of your scenario. Choose the table from the list Make shows you and new entries start flowing to the next modules without anyone exporting a thing.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and never more often than that on the Free plan.
When to use it
your team logs orders or purchase requests in a formatted table and each line should create a task or a message elsewhere.
Watch out
it reads a table, not loose cells; for data typed on a plain sheet, pick Watch Worksheet Rows.
Microsoft 365 Excel2Watch Workbooks

Watch Workbooks

Scheduled trigger

In MakeTriggers when a workbook is created.

A freshly created workbook becomes the starting point of a routine: the file travels as a bundle, ready for the next module to label it, fill it or announce it to the team.

How it fires
scheduled. Make asks Excel for new workbooks on the scenario's schedule, so a file shows up at the next check rather than the second it is saved.
When to use it
each new client or project file should get a standard tab, a line in a register or a heads-up in your team chat.
Watch out
every workbook it returns runs through all the following modules, and each module run counts as an operation on your plan.
Microsoft 365 Excel3Watch Worksheet Rows

Watch Worksheet Rows

Scheduled trigger

In MakeTriggers when a new row is added to a worksheet.

Lines typed into a plain worksheet reach your scenario on their own. Each new row travels as a separate bundle, so the next module deals with entries one at a time instead of a whole sheet.

How it fires
scheduled. Make reads the worksheet on the scenario's schedule and brings through the rows added since its previous check.
When to use it
a colleague enters leads or expenses by hand in a sheet that was never formatted as a table.
Watch out
if the same scenario writes back into that worksheet, its own rows can start it again; send the output to another sheet or workbook.
Modules

What Microsoft 365 Excel can do in Make

Microsoft 365 Excel gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft 365 Excel1

Add a Table

Action

In MakeAdds a new table.

A plain range of cells becomes a proper Excel table that people can sort and filter, and that other modules can target later. It prepares the ground before any data arrives.

When to use it
a scenario has just created a worksheet and its data area should be ready before Add a Table Row starts writing lines into it.
Microsoft 365 Excel2

Add a Table Column

Action

In MakeAdds a new table column.

Your table gains an extra column without anyone opening the file, which keeps a tracker in step with a process that now records something new, such as a status or an owner.

When to use it
another app starts sending a piece of information your existing table has no place for yet.
Watch out
other scenarios reading this table will see the new column as well.
Microsoft 365 Excel3

Add a Table Row

Action

In MakeAdds a new table row.

Data from any other app lands as a new line in your table, mapped column by column. It is the natural last step when Excel is where your data should end up.

When to use it
a form reply, a paid invoice or a new lead should be logged in a shared sheet each time the scenario runs.
Watch out
if Watch Table Rows watches that same table in another scenario, this new row will start that one at its next check.
Microsoft 365 Excel4

Add a Worksheet

Action

In MakeAdds a new worksheet to a workbook.

A new tab appears in the workbook you point to, empty and ready to receive data. One shared file stays organized with a tab per client or per project.

When to use it
a contract gets signed and that client deserves a sheet of their own.
Watch out
check with List Worksheets that the tab does not exist yet, or two runs give you two similar tabs.
Microsoft 365 Excel5

Add a Worksheet Row

Action

In MakeAdds a new worksheet row.

You get a new line on a plain worksheet, no table needed. It suits the simple sheets many teams use as they are, without any formatting.

When to use it
incoming requests should be logged on the sheet a colleague already keeps by hand.
Watch out
when your data already sits inside a formatted table, Add a Table Row is the better fit.
Microsoft 365 Excel6

Delete a Table

Action

In MakeDeletes a table.

A table you no longer need disappears, so a workbook built by a scenario stays readable. Pair it with List Tables to find the right one first.

When to use it
a temporary table used for an intermediate calculation has served its purpose.
Watch out
treat the deletion as final and try it on a copy of the workbook before switching the scenario on.
Microsoft 365 Excel7

Delete a Worksheet Row

Action

In MakeDeletes a worksheet row.

One line leaves the worksheet, such as a cancelled order or a duplicate entry, and your sheet keeps only the rows that still matter.

When to use it
a cancellation recorded in another app should remove the matching line in Excel.
Watch out
locate the row first with List Worksheet Rows; a loose match removes the wrong line.
Microsoft 365 Excel8

Download a Workbook

Action

In MakeDownloads the content of a specified Excel workbook.

You receive the content of a chosen workbook as a file the next module can attach, store or send. The Excel file leaves Excel without a manual export.

When to use it
the latest version of a report should go to a client by email or into cloud storage.
Watch out
on the Free plan Make handles files up to 5 MB, so check the weight of large workbooks.
Microsoft 365 Excel9

Get a Table

Action

In MakeGets the metadata of a specified table.

Returns the metadata of one table rather than its rows, so the scenario knows what it is about to work on before it changes anything.

When to use it
confirm a table exists and read its details before Update a Table or Update a Table Column touches it.
Watch out
to get the actual lines, go for List Table Rows instead.
Microsoft 365 Excel10

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Opens the rest of the Excel API to your scenario, using the connection you already set up. It fills the gap when none of the listed modules does what you need.

When to use it
Excel offers an operation that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the API documentation open and test every call with Run once.
Microsoft 365 Excel11

Update a Table

Action

In MakeUpdates an existing table.

An existing table changes without anyone editing it by hand. It is the follow-up to Get a Table, once you know the current state of what you modify.

When to use it
a reporting scenario must adjust a table it created earlier in the same workbook.
Watch out
the change lands in the shared file everyone opens, so try it on a copy first.
Microsoft 365 Excel12

Update a Table Column

Action

In MakeUpdates an existing table column.

One column of a table gets edited in place while the rest stays as it was. Useful when a column's setup has to follow a change decided elsewhere.

When to use it
a status column needs to be reworked after the process in another app evolves.
Watch out
run Get a Table first so you target the right table and column.
Microsoft 365 Excel13

Update a Worksheet Row

Action

In MakeUpdates an existing worksheet row.

A line already in the sheet receives fresh values instead of a duplicate below it, so your tracker keeps exactly one row per item.

When to use it
a payment status or a delivery date changes in another app and the matching row should follow.
Watch out
the module needs to know which row to change; find it first with List Worksheet Rows.
Microsoft 365 Excel14

List Table Rows

Search

In MakeRetrieves a list of all table rows in a workbook.

Every row of a table comes back, each as its own bundle, ready for the next module to process one after the other.

When to use it
each open item of a tracker should become a message, a task or a record in another tool.
Watch out
a search returns zero, one or many bundles, and every bundle costs operations in the modules that follow.
Microsoft 365 Excel15

List Tables

Search

In MakeRetrieves a list of all table objects.

Gives you the tables present in a workbook, so the scenario can pick the right one before acting on it instead of guessing.

When to use it
just before Delete a Table or Update a Table, to make sure the target exists.
Watch out
a workbook without tables returns nothing, and the modules after it then have no bundle to work on.
Microsoft 365 Excel16

List Worksheet Rows

Search

In MakeRetrieves a list of worksheet rows.

The rows of a plain worksheet come back one bundle each, which lets the scenario spot the line it should change or remove.

When to use it
look up a row before Update a Worksheet Row or Delete a Worksheet Row acts on it.
Watch out
several rows can come back, and each one runs through every module placed after it.
Microsoft 365 Excel17

List Worksheets

Search

In MakeRetrieves a list of worksheet objects.

Returns the tabs of a workbook, so the scenario knows where it can write and which sheets already exist.

When to use it
check whether a client already has a tab before Add a Worksheet creates a second one.
Watch out
each tab arrives as a separate bundle, so the modules after it run once per worksheet.
Microsoft 365 Excel18

Retrieve Data

Search

In MakeRetrieves data for a given range.

Reads the range you define, a totals block for instance, and hands its values to the rest of the scenario. You get the figures without opening the file.

When to use it
the summary of a budget should feed a message or a report built in another app.
Watch out
the range stays fixed; if your summary moves in the sheet, update the range in the module.
Microsoft 365 Excel19

Search Workbooks

Search

In MakeSearches for Excel workbooks.

Finds Excel workbooks for you, so a scenario can locate the right file before it reads or writes anything in it.

When to use it
the file changes from one client to the next and the scenario first has to find the matching workbook.
Watch out
several workbooks may match, and the following modules then run once for each result.
Need help

Need help automating Microsoft 365 Excel with Make?

A person reads every message.

FAQ

Questions about Microsoft 365 Excel and Make

01Is the Microsoft 365 Excel Make integration free?
Yes. Microsoft 365 Excel is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and lift the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. Your Microsoft subscription is a separate matter this page does not cover.
02What do you need to connect Microsoft 365 Excel to Make?
A Make account and a Microsoft account that can open the workbooks you plan to automate. The official documentation lists no other prerequisite. Add any Excel module, click Create a connection, name it if you want, authorize Make on the page that opens and click Save. That single connection then serves all 22 modules, triggers included, so you set it up once per account. If a module later shows no workbooks, the first thing to check is which account you authorized.
03Do Microsoft 365 Excel triggers fire instantly in Make?
No. The 3 triggers, Watch Table Rows, Watch Workbooks and Watch Worksheet Rows, are all scheduled: Make checks Excel on the scenario's schedule instead of waiting for Excel to call it. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan, while paid plans go down to 1 minute. For logs and trackers that gap rarely matters. When a row has to move faster, start the scenario from the app where the data is born and let Excel be the destination.
04What if a Microsoft 365 Excel module is missing in Make?
Use Make an API Call. This module reaches any endpoint of the Excel API with the same connection, so an operation without a dedicated module is still within reach. You write the request yourself, which means reading the API documentation and testing with Run once. The Make documentation gives no numeric limit for this app, so check the behavior on a copy of your workbook before switching the scenario on. If Excel is not the right home for the data, another spreadsheet or database app can take over.
05Make or n8n for Microsoft 365 Excel?
It depends on where your team already builds. Make covers Microsoft 365 Excel with 22 ready modules, 3 scheduled triggers among them, plus Make an API Call for the rest. The same app often has an n8n node too, so both tools can carry a typical Excel workflow. The honest criteria are practical: the tool your team already knows, the other apps in the flow and who will maintain the automation. The comparison linked higher on this page sets the two side by side without ranking them.