Turn people who engage with your posts into CRM contacts

Once a day, the latest export from the PhantomBuster Phantom that collects the people who liked or commented on your posts is read, each person is checked for a verified work email, and the ones it can stand behind are filed as HubSpot contacts.

You get a HubSpot contact with the name, company and profile link exactly as they appear in your export, plus an email that comes only from Dropcontact and only when reported as that person's own work address. Nobody is added without one. HubSpot is asked first whether the address is already on a contact: anyone already there is left exactly as they are, and if HubSpot cannot answer the person is skipped rather than risk a duplicate. Nothing is scored or inferred about anyone, and re-running over the same export adds nobody twice.

Keep the Phantom scheduled inside PhantomBuster: the workflow reads its most recent output rather than launching it, and each run looks up a bounded number of people.

Run every 24 hours.Run every 24 hours.

Set engagementPhantomId to blank.Set engagementPhantomId to blank.

Set maxPeoplePerRun to 25.Set maxPeoplePerRun to 25.

PhantomBusterGet results for Phantom engagementPhantomId. Save it as export.Get results for Phantom engagementPhantomId. Save it as export.

Set engagers to export.rows.Set engagers to export.rows.

Set considered to 0.Set considered to 0.

Set addedCount to 0.Set addedCount to 0.

For each engager in engagers:For each engager in engagers:

If considered multiplied by 1 is greater than or equal to maxPeoplePerRun…If considered multiplied by 1 is greater than or equal to maxPeoplePerRun…

Yes

Stop repeating.Stop repeating.

No

No steps

Add 1 to considered.Add 1 to considered.

Trim engager.firstName and save it as firstName.Trim engager.firstName and save it as firstName.

If firstName is nullIf firstName is null

Yes

Change firstName to blank.Change firstName to blank.

No

No steps

Trim engager.lastName and save it as lastName.Trim engager.lastName and save it as lastName.

If lastName is nullIf lastName is null

Yes

Change lastName to blank.Change lastName to blank.

No

No steps

Trim engager.companyName and save it as companyName.Trim engager.companyName and save it as companyName.

If companyName is nullIf companyName is null

Yes

Change companyName to blank.Change companyName to blank.

No

No steps

Trim engager.profileUrl and save it as profileUrl.Trim engager.profileUrl and save it as profileUrl.

If profileUrl is nullIf profileUrl is null

Yes

Change profileUrl to blank.Change profileUrl to blank.

No

No steps

Trim firstName lastName and save it as personLabel.Trim firstName lastName and save it as personLabel.

If personLabel is emptyIf personLabel is empty

Yes

Show in the output: Skipped an exported row that carried no name, so there was nobody to look up..Show in the output: Skipped an exported row that carried no name, so there was nobody to look up..

Skip to the next item.Skip to the next item.

No

No steps

Set verifiedEmails to an empty list.Set verifiedEmails to an empty list.

If a step below fails, save the error as enrichErrorIf a step below fails, save the error as enrichError

Try

DropcontactEnrich contact firstName. Save it as enrichment.Enrich contact firstName. Save it as enrichment.

Change verifiedEmails to enrichment.contact.email.Change verifiedEmails to enrichment.contact.email.

On error

Show in the output: Could not check for a verified work email for personLabel plus : enrichError.message.Show in the output: Could not check for a verified work email for personLabel plus : enrichError.message.

Set workEmail to blank.Set workEmail to blank.

Set emailQuality to blank.Set emailQuality to blank.

For each candidate in verifiedEmails:For each candidate in verifiedEmails:

Trim candidate.email and save it as workEmail.Trim candidate.email and save it as workEmail.

Trim candidate.qualification and save it as emailQuality.Trim candidate.qualification and save it as emailQuality.

Stop repeating.Stop repeating.

If workEmail is nullIf workEmail is null

Yes

Change workEmail to blank.Change workEmail to blank.

No

No steps

If emailQuality is not nominative@pro or workEmail is empty or workEmail…If emailQuality is not nominative@pro or workEmail is empty or workEmail…

Yes

Show in the output: No verified work address came back for personLabel - nothing was added to HubSpot. An address is only used when the enrichment tool reports it as that person's own work address.Show in the output: No verified work address came back for personLabel - nothing was added to HubSpot. An address is only used when the enrichment tool reports it as that person's own work address.

Skip to the next item.Skip to the next item.

No

No steps

Set existingContactId to blank.Set existingContactId to blank.

Set crmDecision to skip.Set crmDecision to skip.

If a step below fails, save the error as lookupErrorIf a step below fails, save the error as lookupError

Try

HubSpotFind the contact workEmail. Save it as existingContact.Find the contact workEmail. Save it as existingContact.

Trim existingContact.id and save it as existingContactId.Trim existingContact.id and save it as existingContactId.

On error

If lookupError.message contains No contact found (ignoring case)If lookupError.message contains No contact found (ignoring case)

Yes

Change crmDecision to create.Change crmDecision to create.

No

Show in the output: Could not check HubSpot for workEmail plus - leaving them alone rather than risking a duplicate: lookupError.message.Show in the output: Could not check HubSpot for workEmail plus - leaving them alone rather than risking a duplicate: lookupError.message.

If existingContactId is nullIf existingContactId is null

Yes

Change existingContactId to blank.Change existingContactId to blank.

No

No steps

If existingContactId isn't emptyIf existingContactId isn't empty

Yes

Show in the output: workEmail is already in HubSpot as contact existingContactId - the existing record was left untouched.Show in the output: workEmail is already in HubSpot as contact existingContactId - the existing record was left untouched.

Skip to the next item.Skip to the next item.

No

No steps

If crmDecision is not createIf crmDecision is not create

Yes

Show in the output: Left workEmail alone: HubSpot did not confirm they are absent from the CRM, so adding them could have created a duplicate.Show in the output: Left workEmail alone: HubSpot did not confirm they are absent from the CRM, so adding them could have created a duplicate.

Skip to the next item.Skip to the next item.

No

No steps

Set newContactId to blank.Set newContactId to blank.

Set createFailure to blank.Set createFailure to blank.

If a step below fails, save the error as createErrorIf a step below fails, save the error as createError

Try

HubSpotCreate the contact workEmail. Save it as createdContact.Create the contact workEmail. Save it as createdContact.

Trim createdContact.id and save it as newContactId.Trim createdContact.id and save it as newContactId.

On error

Trim createError.message and save it as createFailure.Trim createError.message and save it as createFailure.

If newContactId is nullIf newContactId is null

Yes

Change newContactId to blank.Change newContactId to blank.

No

No steps

If createFailure isn't emptyIf createFailure isn't empty

Yes

Show in the output: Could not add workEmail to HubSpot: createFailure.Show in the output: Could not add workEmail to HubSpot: createFailure.

Else if @newContactId isn't empty

Add 1 to addedCount.Add 1 to addedCount.

Show in the output: Added personLabel (workEmail) to HubSpot as contact newContactId.Show in the output: Added personLabel (workEmail) to HubSpot as contact newContactId.

Otherwise

Show in the output: HubSpot accepted workEmail but returned no contact id, so this run cannot confirm the record was created. Check HubSpot before running it again.Show in the output: HubSpot accepted workEmail but returned no contact id, so this run cannot confirm the record was created. Check HubSpot before running it again.

Show in the output: Looked at considered as text plus people who engaged with your posts and added addedCount as text new HubSpot contacts.Show in the output: Looked at considered as text plus people who engaged with your posts and added addedCount as text new HubSpot contacts.