Read our GETTING STARTED GUIDE first!
SUPPORTED INSIGHTLY INTEGRATIONS
HOW TO AUTHORIZE INSIGHTLY IN PIESYNC
We simply ask your login details and permission for access. For Insightly, we need your API key which you can find under "user settings" within Insightly. When you click "Authorize Insightly", a pop-up window appears that visualizes where to find this information in Insightly.
If you already authorized Insightly in the past or in any other PieSync integration, you'll be able to skip this step and choose from your CONNECTED ACCOUNTS.
SUPPORTED FILTERS TO DETERMINE CONTACT SUBSET TO SYNC WITH = IF
- CONTACT OWNERSHIP
- LINK STATUS
- FIELDS (INCLUDING CUSTOM FIELDS)
- ALREADY EXISTING IN APP YOU SYNC WITH
SUPPORTED ACTIONS = THEN
- UPDATE FIELDS (INCLUDING CUSTOM* FIELDS)
* Except for custom list/drop-down fields. Here's why.
DEFAULT FIELD MAPPING
Depending on the other app you're syncing with, you'll see a number of standard Insightly fields being mapped. For instance, a connection to Office 365 Outlook.com will look something 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 Insightly 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. More information on Customizable Field Mapping here.
In connections with Insightly where adding a tag in app B is a supported trigger, you are able to sync unsubscribes one-way. When a contact unsubscribes in Insightly, we add the tag 'PieSync Unsubscribes' to that same contact in app B. You will be able to review this segment first before e.g. deleting or taking action on that side of the sync.
The availability of this feature is app and connection dependent. If the feature box (screenshots above) is not there to tick, it's simply not possible. We need to be able to detect deletions on one side and at the same time be able to create add the tag 'PieSync Trash' on the other side. More Information on Syncing Deletions in other integrations here.