Use a Zap to send location details from another app to Storepoint. A Zap is a workflow that runs when something happens in your app, such as a record being added or changed. See the Zapier integration overview for examples.
You’ll need: a Storepoint store locator account, a Zapier account, and an app that can send a location’s name, address, and permanent record ID. Your app and Zap steps may require paid plans.
1. Add Storepoint to Zapier
Open the Storepoint Zapier invitation and accept it. Storepoint will then appear as an Invite Only app when you add a Zap action.
2. Connect your locator
- In Storepoint, open Apps & integrations → Zapier.
- Add a source for this workflow, such as Casa Giulina stockists.
- Select Create connection key and copy the key. Keep it private.
- In Zapier, choose Storepoint and paste the key when asked to connect.
3. Build your Zap
Choose a trigger in your app that sends new or changed location records. Then add these Storepoint actions. Use the same Storepoint connection for both.
| Zap step | What to choose |
|---|---|
| Your app’s trigger | The event that sends a new or changed location |
| Storepoint → Find Location | Use the record’s permanent ID as External Reference. Turn on Create if it doesn’t exist and supply the name and address. |
| Storepoint → Update Location | Set Location to the Storepoint Location ID returned by Find. Match the details you want to update. |
For example, use CG-0042 every time your app sends the same store. That lets Storepoint find the location and update its details.
4. Test and turn it on
- Set Visibility: Draft in the create-if-missing fields. Leave Visibility blank in Update while testing.
- Run the Zap with one location. Change its phone number in your app and run it again with the same record ID.
- Check Storepoint: you should see one location with the new number.
- Set Visibility: Published in the final Storepoint step when you are ready. Test that step, then turn on the Zap.
Follow the website embed guide to show your locator on your site.
Setup questions
Which value should I use for External Reference?
Use your app’s permanent record ID or a Store ID you keep unchanged. Names, addresses, and spreadsheet row numbers can change, so use a separate ID for matching. Storepoint matches IDs exactly: 0042 and 42 are different. Reuse the same ID and Storepoint connection in each run.
Can I make a Zap that only adds new locations?
Yes. Use your app’s new-record trigger followed by Create Location. Use Find and Update for a workflow that also maintains existing locations. Some apps need separate triggers or Zaps for new records and changes.
How do I clear a value in Update Location?
Use Clear These Details to remove a supported value. A blank Update field keeps the value already in Storepoint. When changing an address, send the full new address. For tags, send the full list you want. Updating one custom field leaves other custom values in place.
How do I hide a location through Zapier?
Use a trigger that sends the location’s status change, then Update Location with Visibility: Draft. Test it with the same location ID. Storepoint’s Zapier app offers Find, Create, and Update; deleting a record in your app does not automatically remove its location. A filter that skips a record also leaves its existing map listing in place.
Can I send existing records through my Zap?
That depends on your app’s trigger and Zapier’s options for sending older records. Start with one record and check the result. The trigger also controls when future changes are sent. Your Storepoint connection manages the locations in its own source.
Where can I check my Zap’s updates?
Check the run in Zapier and its location in Storepoint. Use the same Storepoint connection in Find and Update. If you replay an older run, send the current record again afterward so the latest details appear on your map.