SharpSpring

GETTING STARTED GUIDE: How to set up a new connection? 
ALL FEATURES EXPLAINED: All our features/functionality explained in detail - no app-specifics. 

SharpSpring is a powerful marketing solution with outstanding automation including great features such as behaviour-based email marketing, dynamic forms, landing page creating, blog building and CRM. Relevant analytics give you great insights on all of this functionality allowing you to improve and stay on top of your game continuously!

Below you'll find detailed information, specifically for SharpSpring integrations:

Supported SharpSpring Integrations


Authorizing SharpSpring

We simply ask your login details and your permission. We need your API ID and API key: you can find both under 'settings' - ‘SharpSpring API’ within your account. API access is available for all SharpSpring users.

If you already authorized SharpSpring account(s) in the past or in any other PieSync integration, you'll be able to the first part of the authorization and choose from your CONNECTED ACCOUNTS.

[IF] Supported Conditions/Filters

  • SUBSCRIBED TO/UNSUBSCRIBED FROM EMAILS
  • IN/OUT OF A LIST
  • LEAD SCORE/STATUS
  • OWNERSHIP
  • HAS/DOES NOT HAVE OPPORTUNITIES
  • ASSIGNED/UNASSIGNED
  • FIELD VALUES (INCLUDING CUSTOM FIELDS)
  • ALREADY EXISTING IN APP YOU SYNC WITH 


[THEN] Supported Actions

  • ADDING TO/REMOVING FROM LIST
  • ASSIGN TO
  • UPDATE LEAD STATUS
  • UPDATING FIELD VALUES (INCLUDING CUSTOM FIELDS)

Default Field Mapping

Depending on the other app you're syncing with, you'll see a number of standard SharpSpring fields being mapped by default. For instance, in a connection with Google Contacts, the default field mapping looks like this:

PieSync syncs the default name field(s) that come with the apps. Sometimes they have a different structure in both apps you connect. E.g. first and last names are separate in app A and joint in a single field in app B. In the background, PieSync joins first and last names together from app A to B and separates them again from app B to A. Our algorithm is smart about which part it updates in app B

Customizable Field Mapping

You can custom map your SharpSpring Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping HERE

Additional Options

Syncing Unsubscribes/Deletions

Currently, there are no Sharpspring integrations on the PieSync platform that support our Deletions sync.

In some connections with SharpSpring, you are able to SYNC UNSUBSCRIBES one-way. When a contact gets unsubscribed in SharpSpring, we add the tag 'PieSync Unsubscribes'  to that same contact in the other app. You will be able to review this segment first before taking any action in the other app too. 

The availability to Sync Unsubscribes/Deletions is app and connection dependent. If the box (screenshots above) is not there to tick, it's simply not possible. We need to be able to detect unsubscribes/deletions on one side and at the same time be able to create add the tag 'PieSync Unsubscribes' or ‘PieSync Trash’ on the other side. More Information on Syncing Unsubscribes here or on Deletions here.


Thanks to the feedback we have already received, we created a list of popular apps that we’re going to work on very soon. By voting them up in our pipeline, YOU decide which connectors we’ll release first. If you don’t see your app on the list or need any further help, drop us a line - support@piesync.com.  Don't forget to read our blog for the latest in productivity, apps, and technology!

How did we do?