Turn people who engage with your posts into CRM contacts

Your posts pull in people who are already paying attention to you, and almost none of them ever reach the CRM. Once a day this workflow reads the latest export from the PhantomBuster Phantom you already use to collect the people who liked or commented on your posts, looks each one up, and files the ones it can stand behind as HubSpot contacts.

It is deliberately conservative about what it writes down. The name, company and profile link come straight from your export and are never guessed or embellished. The email address is never constructed from a name and a domain: it comes from Dropcontact, and only when Dropcontact reports it as that person's own work address rather than a generic or personal one. Anyone without one is reported in the run and left out of the CRM entirely. Nothing is scored, rated or inferred about any individual, and no company records or deals are created.

Before creating anything it asks HubSpot whether that address is already on a contact. Somebody already in your CRM is left exactly as they are - this never overwrites an existing record. If HubSpot cannot answer the question the person is skipped rather than added, because a duplicate contact is harder to undo than a missed one. The record itself is the marker, so re-running the workflow over the same export adds nobody twice.

Set it up by putting your Phantom's id in the 'engagementPhantomId' step. Keep the Phantom scheduled inside PhantomBuster: this workflow reads whatever its most recent run produced rather than launching it, so a scrape that takes hours cannot stall the workflow. It reads the firstName, lastName, companyName and profileUrl columns, which is what the LinkedIn post likers and post commenters Phantoms export. 'maxPeoplePerRun' bounds how many people one run will look up, so a large export cannot spend your whole enrichment balance in one go. Every decision the run makes - added, already there, no verified address - is written to the run log.