An automatic and bi-directional sync between Hatch and LeadPerfection
Overview:
- Type: CRM
- Version: Prismatic/Hatch App Marketplace
- Set-Up: Enter Credentials
- Sync Frequency: 15 minutes
- SandBox: Yes
Shared Data:
Objects that Sync with Hatch:
- Lead
- Prospect
Any fields or values under these objects will be syncing in Hatch and are available in the Hatch product.
When do LeadPerfection objects sync to Hatch?
The following TRIGGERS cause the listed sync ACTIONS:
- TRIGGER: A LeadPerfection Lead object is updated within the last 20 minutes before the sync began, there is at least one LeadPerfection Prospect object associated with the Lead, and all LeadPerfection fields are available that are mapped to Hatch standard fields (below)
- ACTION: All LeadPerfection Lead object fields/values are sync’d
- ACTION: The associated LeadPerfection Prospect object’s fields/values are sync’d
- In the rare case that there are multiple LeadPerfection Prospect objects associated with the Lead object, Hatch creates one opportunity for every combination of Lead and Prospect
- TRIGGER: A LeadPerfection Prospect object is updated within the last 20 minutes before the sync began, was not associated with a LeadPerfection Lead object during the sync, and all LeadPerfection fields are available that are mapped to Hatch standard fields (below)
- ACTION: All LeadPerfection Prospect object fields/values are sync’d
LeadPerfection to Hatch Opportunities
Creating a Hatch Opportunity
Sync’d LeadPerfection objects will be joined into a single Hatch opportunity in one of the following combinations:
- Lead + Prospect
- Prospect
Updating a Hatch Opportunity
The integration will update an existing Hatch opportunity when:
- The sync’d External ID matches the existing opportunity’s External ID
- The sync’d External Created At matches the existing opportunity’s External Created At
Adding an additional Hatch Opportunity (Opp Sorting)
The integration will create an additional (new) Hatch opportunity when:
- The sync’d External ID does not match the existing opportunity’s External ID
- The sync’d External Created At does not match the existing opportunity’s External Created At
Hatch Opportunities to LeadPerfection Field Mapping
The following Hatch standard fields are mapped from LeadPerfection data (on every Hatch opportunity):
| Hatch Field | LeadPerfection Field |
|
Prospect.email |
|
| External ID |
Prospect.leads[0].id |
| External Contact ID |
Prospect.cst_id |
| External Created At |
Prospect.dateadded |
| External Updated At (Used for Opp Sorting) |
Prospect.lastchanged Prospect.leads[0].lastchangedon (if above is missing) Prospect.leads[0].dateentered (if above is missing) Prospect.leads[0].jobs[0].contractdate (if above is missing) Prospect.leads[0].appointments[0].lastchangedon (if above is missing) |
| First Name |
Prospect.firstname |
| Last Name | Prospect.lastname |
| Phone |
Prospect.phone1 |
| Status |
Prospect.leads[0].disposition |
What can be customized in LeadPerfection Integration Settings in Hatch:
User options
- Push Communications — A true/false flag that indicates if the integration should push communication data back to LeadPerfection (default is true)
- Push To Call Logs — A true/false flag that indicates if communication data pushed to LeadPerfection should be created as a Call Log object (default is false)
- Push To Notes — A true/false flag that indicates if communication data pushed to LeadPerfection should be created as a Note on the Prospect object (default is true)
- Push To Production Notes — A true/false flag that indicates if communication data pushed to LeadPerfection should be created as a Note on the first Job object in the Lead object (default is false)
Admin options
- Sync Schedule — The schedule that dictates how often the integration attempts to sync (default is every 15 minutes)