Connect n8n to My Store Locator

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)

Install the community node

Our community node is published on npm as n8n-nodes-mystorelocator. It adds the My Store Locator node (locations, maps, enquiries, categories, statuses) and two triggers: one that polls for new or changed data, and a real-time webhook trigger.

1. In your self-hosted n8n instance, open Settings → Community Nodes and click Install.
2. Enter the package name n8n-nodes-mystorelocator, confirm the notice and click Install.
3. Create the My Store Locator API credentials with your API key.

Without the user interface, install the package in the ~/.n8n/nodes folder:

npm install n8n-nodes-mystorelocator

n8n Cloud only shows community nodes that n8n has verified. There, use the Webhook and HTTP Request nodes as described below.

Trigger: an event from My Store Locator

1. Create a workflow in n8n and add a Webhook node as the start, method POST.
2. Copy the node's Production URL (it must be publicly reachable over https).
3. In My Store Locator, create a webhook with that URL under API & Webhooks, format JSON, and choose the events.
4. Activate the workflow and send a test event from the app.

To verify the signature, compute the HMAC-SHA256 of <t>.<body> with the webhook's secret in a Code node and compare it with the X-MSL-Signature header.

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 n8n, create a Header Auth credential: name Authorization, value Bearer msl_live_….
3. Add an HTTP Request node: method POST, URL https://app.my-store-locator.com/api/v1/ext/locations, authentication with that Header Auth.
4. Turn on Send Body, format JSON, and map the fields from previous nodes.

To update a location, use PATCH with /api/v1/ext/locations/{id}. To test the connection, GET /api/v1/ext/me is enough.

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.

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

FAQ