Integration Types

Mapsly offers a variety of integration options ranging from turnkey native connectors to file-based imports

Mapsly offers several integration options:

  • Bi-directional real-time connectors to the most popular CRMs
  • Through Zapier
  • Using Mapsly API
  • Through regular imports of CSV files
  • Polling, where Mapsly will pull data from your data source’s API endpoints

View the full list of tested integrations here.

Bi-directional real-time connectors

The Mapsly team developed connectors to the most popular CRMs, so you can start using Mapsly in minutes. These connectors automatically configure your Mapsly organization’s objects and fields to match the data structure of your data source and keep your data structure up-to-date as you add or remove objects and fields in your data source.

Mapsly provides a detailed setup guide and a sign-up wizard for each of the data sources with such connectors.

When signing up for a new Mapsly account, you’ll be able to pick objects and fields to be added to your Mapsly organization and synced with your data source.

Once set up, a connector also automatically pulls new and updated records from your data source into Mapsly, and syncs removed records. All connectors support regular syncs (by default, set to sync every 30 minutes, but can be reduced to every 10 minutes), while some connectors, like HubSpot, support real-time sync from the data source to Mapsly.

Also, once set up, a connector will push new records that you may create in Mapsly and update existing records made in Mapsly to the data source in real-time. (All connectors support real-time sync from Mapsly to the data source.)

Zapier-based integration

Zapier is a popular integration platform that allows one system that offers triggers to pass data to another system that offers actions. Any IT system integrated with Zapier, not only a CRM or CMS, can be a data source to Mapsly, and 40+ CRMs are already to connected to Zapier.

Using Zapier, you can create, update or remove records of any objects that your data source’s Zapier integration supports.

Before a Zapier-based integration can be set up in Mapsly, you’ll need to configure objects and fields in Mapsly that you’d like to import to Mapsly from your data source. Once it’s done, you’ll be able to configure to create new records and update existing records in any of these objects in Mapsly.

Actions that are not supported by your data source’s Zapier integration, for example removing a record (which is often the case), can be implemented by a direct call to the Mapsly API.

Data that you edit in Mapsly, including assigned territories, can be pushed to your data source using Zapier or Masply webhooks. This feature is currently in closed beta, so please contact us in chat or at [email protected] to request it for your Mapsly organization.

API-based integration

Mapsly offers a simple-to-use API that you can use to create, update, and remove records in Mapsly. Learn more about the API on our developer portal.

Changes made via the API are reflected on the map in real time, so you may use the API for real-time fleet tracking.

API can also be used in conjunction with a connector to enable real-time data sync to Mapsly for data sources that support webhooks like Zoho CRM or with Zapier.

Regular imports of CSV files

Mapsly also offers an integration option based on regular imports of CSV files that can be automatically exported from your system (this may require some development on the side of your data source). This option is in closed beta, so please contact us to request it for your Mapsly organization. 

If you need to import data manually exported from your data source, please use our Google Sheets connector (setup guide).

Polling API endpoints in your data source

You may set up Mapsly to regularly query API endpoints implemented in your data source and pull new and updated records from there, as well as sync removed records.

This option is in closed beta, so please contact us to request it for your Mapsly organization.