Resources · Make integration

Meraki Make integrationAutomate Meraki with Make.

What can the Meraki Make integration do for the people who run your network? It gives you 9 modules, 8 actions and 1 search, to handle organizations and networks without code. This guide links your API key, builds a first scenario and explains when each module fits.

Try the Meraki integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Meraki Make integration automate?

The Meraki Make integration connects your Meraki account to Make, a no-code tool where you chain modules into a scenario. A scenario is the automation you build, and a module is one brick of it. With Meraki, those bricks create, read, update and delete organizations and networks from your account, in response to what happens in your other apps.

Keep an inventory without copying it by hand. List Organizations returns every organization your key can see, and Get an Organization or Get a Network pulls the details of one. Send the result to a spreadsheet or a report app, and the inventory follows your account instead of someone's memory.

Turn a request into a change. When a ticket or a form in another app asks for a network change, Update a Network applies it, and Update an Organization does the same one level up. The request stays the record of who asked for what.

Open and close accounts in one flow. Create an Organization sets up a new one when a deal is signed elsewhere; Delete an Organization and Delete a Network clean up when it ends. Put a human approval step before any delete.

What Make does not give you here: Meraki has no trigger in Make, so Make cannot watch the account for changes by itself. A scenario starts on a schedule or on another app's event. For any endpoint the listed modules skip, Make an API Call reuses the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains operations, and the Make training covers scenario building step by step.

Connect

How do you connect Meraki to Make?

  1. 01

    Add a Meraki module

    Log in to Make, open your scenario and add any Meraki module, for example Get an Organization. In the module panel, click Create a connection. A connection is your Meraki account linked to Make once, then reused by every Meraki module you add later.

  2. 02

    Paste your API key

    You can type a label in Connection name, which is optional but handy when several accounts are linked. Then paste the key you copied from your Meraki account into the API key field. Make needs nothing else from you on this screen.

  3. 03

    Save and confirm access

    Click Save. If Meraki asks you to authenticate or confirm access, accept it in the window that opens. The connection then appears in the module's dropdown, and Make can list the organizations and networks it is allowed to read.

First scenario

Your first scenario with Meraki and Make

GoalWhen a change request lands in another app, Make reads the Meraki network, then applies the update.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, such as your ticketing or form tool, and choose the trigger that fires on a new request.

  2. 02

    Add Get a Network

    Click the + to the right of the trigger, search for Meraki and pick Get a Network. Create the connection with your API key, then map the network named in the request from the previous module.

  3. 03

    Add Update a Network

    Add a second Meraki module, Update a Network. Map the network from Get a Network and the new values from the request. Reading first means you can check what the network looked like before the change.

  4. 04

    Test with Run once

    Submit one test request, then click Run once. Open each module's bubble to read the bundle it received, a bundle being one item passed from module to module. Use a test network for this first run.

  5. 05

    Set the schedule and switch on

    Open Scheduling on the first module. With a scheduled trigger, a new scenario checks every 15 minutes by default, and the Free plan cannot go below that; an instant trigger runs as soon as the request arrives. Switch the scenario on and each new request goes through the same path.

Modules

What each Meraki module does in Make

Meraki gives you 9 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Organizations

5 modules
Meraki1

Create an Organization

Action

In Make“Creates a new organization.”

Sets up a brand new organization in your Meraki account from inside a scenario, so onboarding a site or a client no longer waits for someone to open the dashboard.

When to use it
right after a contract is marked signed in your CRM, as the step that gives the new account its own organization.
Watch out
run it once per new account; a scenario that fires twice on the same deal creates two organizations.
Meraki2

Update an Organization

Action

In Make“Updates an organization.”

Changes an existing organization so the account reflects a decision made in another tool, without anyone logging in to edit it by hand.

When to use it
a client is renamed in your CRM and the organization should follow; map the organization from Get an Organization or List Organizations first.
Watch out
if you need a trace of the old values, run Get an Organization before this step so the scenario history keeps them.
Meraki3

Get an Organization

Action

In Make“Gets an organization.”

Reads one organization and hands its details to the next module as a single bundle. It is the safe way to look before you change anything.

When to use it
ahead of Update an Organization, or to feed one account's details into a report or a message to the team.
Watch out
it targets one organization you already know; to discover all of them, start with List Organizations instead.
Meraki4

List Organizations

Search

In Make“Lists all organizations.”

Returns every organization your API key can reach, one bundle per organization, which makes it the starting point of any inventory or audit scenario.

When to use it
to copy the list into a spreadsheet, or to loop through all organizations and run another module on each.
Watch out
each bundle it returns runs the following modules once, and each run counts as an operation on your Make plan.
Meraki5

Delete an Organization

Action

In Make“Deletes an organization.”

Removes an organization from your Meraki account, the last step of an offboarding flow when an account really closes.

When to use it
after a contract end is confirmed in your CRM and a person has approved the removal in the scenario, never on a raw form entry.
Watch out
a deletion cannot be undone from Make; test on a spare organization and add an approval or a filter before this module.

Networks

3 modules
Meraki6

Update a Network

Action

In Make“Updates a network.”

Applies a change to one network, which turns a request written in a ticket or a form into the actual edit in Meraki.

When to use it
when a site manager files a change and your team wants it applied the same way every time, with the request kept as the record.
Watch out
map the network from Get a Network rather than typing it, or one scenario may update the wrong site.
Meraki7

Get a Network

Action

In Make“Gets a network.”

Fetches the details of one network and passes them on, so later modules work from what Meraki really holds and not from what a request claims.

When to use it
as the check before Update a Network, or to post a network's current state to a chat channel when someone asks.
Watch out
no network listing module exists in this app, so you need to know which network you target, from the request or from your own records.
Meraki8

Delete a Network

Action

In Make“Deletes a network.”

Removes one network from its organization, useful when a site closes and the configuration should not linger in the account.

When to use it
at the end of a decommissioning checklist tracked in another app, once every earlier step is ticked.
Watch out
nothing brings the network back from Make; run Get a Network just before so the scenario history keeps a copy of what was removed.

Other

1 module
Meraki9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Meraki API with the connection you already set up, so you are not stuck when the 8 other modules stop short of what you need.

When to use it
for any Meraki endpoint that none of the named modules covers, looked up in the Meraki API reference before you build.
Watch out
you write the request yourself here, so test it with Run once on read-only calls before trying a change.
Need help

Need help automating Meraki with Make?

A person reads every message.

FAQ

Meraki and Make: frequent questions

01Is the Meraki Make integration free?
Yes, Meraki is a standard app, so it works on the Free plan of Make. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, 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 each month. This page gives no price for Meraki itself.
02What do you need to connect Meraki to Make?
You need a Make account, a Meraki account and the API key copied from that Meraki account. Add any Meraki module, click Create a connection, give it a name if you like, paste the key into the API key field and click Save. If Meraki asks you to authenticate and confirm access, accept. The Make documentation lists no other prerequisite, and every Meraki module then reuses that single connection, so you only do this once per account.
03Does the Meraki Make integration react in real time?
No, Meraki has no trigger in Make, so nothing in the app can start a scenario on its own. You start it in one of two ways. The first is a schedule set with the clock on the first module, every 15 minutes by default and never shorter on the Free plan. The second is a trigger from another app, a form or a ticketing tool, placed before the Meraki modules. If that other trigger is instant, the flow starts as soon as the other app calls Make.
04What if a Meraki module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Meraki API with the connection you already created, which covers whatever the 9 listed modules leave out. You write the request yourself, so test it with Run once on a read-only call first. The Make documentation gives no numbered limit for Meraki, and none should be assumed. When a call fails, read the bundle each module received after Run once to see where it stopped.
05Should you pick Make or n8n for Meraki?
It depends on your criteria rather than on a winner. In Make, Meraki comes with 9 modules for organizations and networks plus Make an API Call, and you build everything in a visual editor with plans counted in operations. Before choosing, check whether n8n offers a Meraki node and which objects it covers, and compare how each tool bills and where your team already works. The n8n vs Make comparison on this site sets out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations