Create new leads into SalesForce even if contact exists
SOLVE
Hi, @Kelvine. You're describing a use case that's not very compatible with the connector. As email ends up being the unique identifier between the HubSpot contact and the Salesforce lead or contact, any subsequent activity on a HubSpot contact will continue writing to whatever Salesforce record it's syncing to.
The only way to solve for this is with automation in Salesforce, either declarative or code. You'll want it to fire on a task create, look for duplicate tasks on the lead or contact, then create a new lead when that happens. (If you attempt this, leave the default email field blank on the duplicate record. Otherwise, all you'll do is change the association to the duplicate lead.)
Unfortunately, this isn't a quick setup, but it could be done. Apex is likely more robust than Flow amd Process Builder.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.
Create new leads into SalesForce even if contact exists
SOLVE
Hi, @Kelvine. You're describing a use case that's not very compatible with the connector. As email ends up being the unique identifier between the HubSpot contact and the Salesforce lead or contact, any subsequent activity on a HubSpot contact will continue writing to whatever Salesforce record it's syncing to.
The only way to solve for this is with automation in Salesforce, either declarative or code. You'll want it to fire on a task create, look for duplicate tasks on the lead or contact, then create a new lead when that happens. (If you attempt this, leave the default email field blank on the duplicate record. Otherwise, all you'll do is change the association to the duplicate lead.)
Unfortunately, this isn't a quick setup, but it could be done. Apex is likely more robust than Flow amd Process Builder.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.