Connect Make to My Store Locator

In Make (formerly Integromat) you connect My Store Locator with the "Webhooks" and "HTTP" modules. We are testing a dedicated Make app.

Available todayWebhooks and the customer API (from Starter) with Make's standard building blocks.

Own app in testingMake app with ready-made modules. We are testing it; it is not published yet.

What you can do with it

  • React to events: a new enquiry from the map becomes a task in your CRM, a message in your team chat or a row in a spreadsheet.
  • Maintain locations automatically: new stores from your ERP, a spreadsheet or a form are created or updated in My Store Locator.
  • Sync: fetch changed locations regularly (updatedSince) and pass them on to other systems.

Before you start

  • A My Store Locator account on the Starter plan or higher - API keys and webhooks are included there (see plans)
  • An API key with the right permissions (in the app under API & Webhooks)

Trigger: an event from My Store Locator

  1. Create a scenario in Make and choose Webhooks → Custom webhook as the first step. Make creates a webhook URL.
  2. In My Store Locator, create a webhook with that URL under API & Webhooks, format JSON, and choose the events.
  3. In Make, click Redetermine data structure and send a test event from the app. Make detects the fields.
  4. Add the following modules, for example Google Sheets, a CRM or email.

Available events: location.created, location.updated, location.deleted, map.published, lead.created, import.finished. Every delivery carries the headers X-MSL-Event and X-MSL-Signature (HMAC-SHA256) so you can verify where it came from. If a delivery fails, we retry after 1, 5 and 30 minutes.

Action: create or update a location

  1. In the app, create an API key with the locations:write permission.
  2. In Make, add the module HTTP → Make a request.
  3. URL https://app.my-store-locator.com/api/v1/ext/locations, method POST.
  4. Under Headers: Authorization = Bearer msl_live_… (your key).
  5. Body type "Raw", Content type "JSON (application/json)", body as JSON with values from previous modules.

To update a location, use PATCH with /api/v1/ext/locations/{id}.

An example body for a new location:

{
  "name": "Store Frankfurt North",
  "street": "Musterstraße 1",
  "zip": "60320",
  "city": "Frankfurt am Main",
  "country": "DE"
}

If coordinates are missing, the address is geocoded by our map server. New locations appear on all published maps unless you name specific maps. All endpoints and fields are listed under API and webhooks.

Note: A dedicated Make integration from My Store Locator with ready-made triggers and actions is in testing and not yet published. Until then the connection works as described above, through webhooks and HTTP requests.

Only occasional bulk updates? CSV import is often enough: export the list, import it, done.

Security

  • Give the API key only the permissions the workflow needs, for example just locations:write.
  • Store the key in Make's credentials, not as plain text in individual steps.
  • Revoke keys you no longer need in the app with one click.

FAQ

Do I need a particular Make plan?

The "Webhooks" and "HTTP" modules are standard Make modules. How many operations you can run depends on your Make plan.

Do API calls count as map views?

No. Map views only count when the public map is loaded. The customer API allows 600 requests per minute per key.

Can I delete locations through the API?

DELETE archives a location, like "Delete" in the app. It then disappears from all maps.

Try it with your own locations.

Create an account, import your locations, embed the map. The Free plan stays free - and you can test Pro for 14 days.

Try the demoTry it now, no sign-up