GETTING STARTED GUIDE: How to set up a new connection?
ALL FEATURES EXPLAINED: All our features/functionality explained in detail - no app-specifics.
Prospect.io organizes the mess of marketing and sales automation with a simple and elegant sales prospecting tool. Find prospect Information and generate leads with the best sales tool for cold emailing and drip campaigns. Increase your sales team productivity!
Below you'll find detailed information, specifically for Prospect.io integrations:
Supported Prospect.io Integrations
We simply ask your login details and your permission. To Authorize your Prospect.io account, we need your API key which can be found in your personal settings.
If you already authorized Prospect.io 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
- CAMPAIGN STATUS
- IN/OUT OF A LIST/CAMPAIGN
- EMAIL STATUS
- CONVERSION/QUALIFICATION/ARCHIVAL STATUS
- FIELD VALUES (INCLUDING CUSTOM FIELDS)
- ALREADY EXISTING IN APP YOU SYNC WITH
[THEN] Supported Actions
- UPDATING LIST/ARCHIVAL/CONVERSION/QUALIFICATION
- 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 Prospect.io 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 Prospect.io 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.
The availability to Sync Unsubscribes/Deletions is app and connection dependent. If the box 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 - email@example.com. Don't forget to read our blog for the latest in productivity, apps, and technology!