Connect Zapier to My Store Locator

With Zapier you can already connect My Store Locator to thousands of other services today - through webhooks and our customer API. We are testing a dedicated Zapier integration.

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

Own integration in testingZapier integration with ready-made triggers and actions. We are testing it; it is not in the Zapier App Directory 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 new Zap in Zapier and choose Webhooks by Zapier → Catch Hook as the trigger. Zapier shows you a webhook URL.
  2. In My Store Locator, create a webhook with that URL under API & Webhooks, format JSON, and choose the events, for example lead.created.
  3. Send a test event from the app and load it in Zapier as a sample.
  4. Add the action you want, for example a CRM record or a Slack message.

According to Zapier, "Webhooks by Zapier" is only available on paid Zapier plans.

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 Zapier, add the action Webhooks by Zapier → Custom Request.
  3. Method POST, URL https://app.my-store-locator.com/api/v1/ext/locations.
  4. Under Headers: Authorization with the value Bearer msl_live_… (your key) and Content-Type with application/json.
  5. Under Data, the body as JSON; map the values from the previous step.

To update a location, use PATCH with /api/v1/ext/locations/{id} and send only the changed fields.

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 Zapier 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 Zapier's credentials, not as plain text in individual steps.
  • Revoke keys you no longer need in the app with one click.

FAQ

Is My Store Locator in the Zapier App Directory?

Not yet. The integration is in testing. Until then, use "Webhooks by Zapier" as described.

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