Resources · Make integration

Woosmap Make integrationAutomate Woosmap with Make.

Keep your Woosmap assets in step with the tools where your data already lives. The Woosmap Make integration gives you 5 modules: 4 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module for each job.

Try the Woosmap integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Woosmap Make integration do for you?

The Woosmap Make integration lets a Make scenario, the automation you build in Make, read and change the assets stored in your Woosmap account. Each step of that scenario is a module: here, 4 actions and 1 search, all using one connection built from a Woosmap API key.

Push new records into Woosmap. When another app hands Make a new item, Upsert Assets sends it to Woosmap. Upsert is short for update or insert, so the same module covers a fresh asset and a changed one.

Look something up before acting. Search Assets returns the matching assets as bundles, the items that flow from one module to the next, and Get an Asset fetches a single one you already know. Both feed later steps with real Woosmap data.

Clean up what no longer belongs. Delete Assets removes assets once the source record is gone. For anything the listed modules skip, Make an API Call reaches any endpoint of the Woosmap API with the same connection.

Woosmap has no trigger in Make, so the scenario starts from a schedule or from another app. Make also warns that its Woosmap documentation is AI-generated and may contain mistakes, so check important details with Woosmap. If you are weighing tools, read n8n vs Make; to learn the editor properly, see Make training, and when a run fails, open Make troubleshooting.

Connect

How do you connect Woosmap to Make?

  1. 01

    Create an API key in Woosmap

    In Woosmap, open the Projects icon in the left menu, pick or create a project, then go to its Security tab. Click Add a Private Key, give it a name, choose its permissions and restriction type, click Add and copy the key.

  2. 02

    Add a Woosmap module in Make

    In your scenario, add any Woosmap module and click Create a connection. The Connection name field is optional, but a clear name helps later if you link several Woosmap projects.

  3. 03

    Paste the key and save

    Paste the key you copied from Woosmap and follow the on-screen instructions to finish. The connection, your Woosmap account linked to Make, is then reused by every Woosmap module you add.

First scenario

Your first scenario with Woosmap

GoalWhen a new record appears in another app, Make creates or updates the matching asset in Woosmap.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Woosmap has no trigger, so this first module comes from the app that holds your source records.

  2. 02

    Add Upsert Assets

    Click the + to the right of that first module, search for Woosmap and pick Upsert Assets. Select your Woosmap connection, or click Create a connection if you have not made one yet.

  3. 03

    Map the data

    Fill the module by mapping values from the first module. Each record that arrives becomes one bundle, and Upsert Assets runs once per bundle, which counts as one operation on your plan.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, then check in Woosmap that the asset looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, and the Free plan does not go below that. Then switch the scenario on.

Modules

What each Woosmap module does

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

Woosmap1

Delete Assets

ActionIn the docs only

Delete Assets clears assets out of your Woosmap account, so Woosmap keeps only what still exists in the source you trust.

When to use it
after a record is closed or archived in the tool that owns your data, place this module at the end of the scenario to remove its counterpart in Woosmap.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a throwaway asset first.
Woosmap2

Get an Asset

ActionIn the docs only

Get an Asset hands you the full record of one Woosmap asset, ready to map into the next module of your scenario.

When to use it
you already know which asset you need, for example because an earlier step gave you its reference, and you want its data without sorting through a list.
Watch out
if you do not know the exact asset, reach for Search Assets instead, since this module targets a single item.
Woosmap3

Make an API Call

ActionIn the docs only

Make an API Call opens the rest of the Woosmap API to your scenario, reusing the connection you already set up, so no second key is needed.

When to use it
the four other modules do not cover the task you have in mind, and you still want to stay inside Make rather than switch tools.
Watch out
you write the request yourself, so keep the Woosmap API documentation open while you fill it in.
Woosmap4

Search Assets

SearchIn the docs only

Search Assets finds the Woosmap assets that match what you are looking for and passes each one on as its own bundle.

When to use it
before an update or a cleanup, when you need to see which assets exist rather than guess.
Watch out
the search can return zero, one or many bundles, and every module after it runs once per bundle, so a broad search spends more operations than you might expect.
Woosmap5

Upsert Assets

ActionIn the docs only

Upsert Assets saves assets into Woosmap whether they are new or already there: the name joins update and insert, so one module covers both cases.

When to use it
another app is the source of truth for your records and Woosmap should mirror it, without you building one branch for creation and another for edits.
Watch out
run it once on a single test record and check the result in Woosmap before you switch the scenario on.
Need help

Need help automating Woosmap with Make?

A person reads every message.

FAQ

Woosmap and Make: frequent questions

01Is the Woosmap Make integration free?
Yes on the Make side. Woosmap is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 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, Enterprise) drop the interval to 1 minute and count usage in credits each month. You still need an active Woosmap account; for its subscription, check Woosmap's own pricing page.
02What does the Woosmap Make integration need to connect?
An active Woosmap account and an API key. In Woosmap, open Projects in the left menu, choose a project, go to the Security tab and click Add a Private Key. Name the key, select its permissions and restriction type, click Add and copy it. In Make, add a Woosmap module, click Create a connection, optionally fill the Connection name field and paste the key. Every Woosmap module then reuses that connection.
03Does Woosmap trigger a Make scenario in real time?
No. Woosmap has no trigger module in Make, so it cannot start a scenario on its own. You have two ways in. Put a schedule on the first module, which runs every 15 minutes by default and never more often than that on the Free plan, or 1 minute at best on paid plans. Or open the scenario with a module from another app, and if that app offers an instant trigger, it calls Make through a webhook as soon as something happens.
04What if a Woosmap module is missing in Make?
Use Make an API Call. It is one of the 5 Woosmap modules and lets the scenario call any endpoint of the Woosmap API, with the same connection as the other modules. You build the request yourself from Woosmap's API documentation. Keep in mind that Make labels its Woosmap documentation as AI-generated and possibly inaccurate, so confirm important details with Woosmap before you rely on them. Since the connection is shared, you do not need a second API key for it.
05Is Make or n8n the better fit for Woosmap?
It depends on where the rest of your automations run. In Make, Woosmap comes with 5 modules, including Make an API Call for anything they leave out, and it works from the Free plan. Apps like Woosmap often have an n8n node too, so check that side before deciding. The fairest test is to build the same small scenario in each tool and keep the one your team reads more easily.
Same platform

Other docs you might need on this stack.

Browse all integrations