# Turn the people who engage with your posts into Pipedrive leads > Every Monday, gather everyone who commented on or reacted to your team's LinkedIn posts, skip the ones already in your CRM, and hand reps the rest. - Workflow type: agent - Services: Boomerang, Pipedrive, Google Sheets, Slack Bot - Categories: Sales, Marketing - Published: 2026-08-31 ## What it does - Collects everyone who commented on or reacted to the LinkedIn posts your team shared in the past week. - Narrows them to people who fit your ideal customer profile and ranks them by intent, so a thoughtful comment outranks a passive reaction. - Checks every name against your CRM first, so you never pay to look up someone your team already knows. - Creates new leads with the person's actual comment and the post it came from attached, then sends one Slack digest that keeps new leads separate from existing contacts who engaged. ## What you'll need - A Boomerang account with credits available - A Pipedrive login that can create people and leads - A Google Sheets spreadsheet with one tab where your team pastes LinkedIn post links, and a second tab that keeps the running record of who has already been processed - A Slack workspace and a channel for the weekly digest - Your ideal customer profile written down, plus a list of your own staff and competitor names to leave out ## Prompt Every Monday at 8am, turn last week's LinkedIn post engagement into ranked Pipedrive pipeline, without paying to enrich anyone we already know. Use a cron trigger. Start in Google Sheets. Use Get Values to read the tab where my team drops LinkedIn post URLs, and take every post added in the past seven days. In the same spreadsheet, also read the ledger tab, which lists every engager already processed in previous runs. Anyone on that ledger is skipped for the rest of this run, so the same person is never enriched twice. For each post URL, call Boomerang Enrich Single Profile twice: once in comments mode and once in reactions mode. Together those give the people who engaged with that post, along with the text of each comment. Boomerang jobs are always asynchronous. Submitting returns a request id with status "In queue", and status is one of exactly "In queue", "Completed", or "Issue", capitalized and with a space. Poll Get Request Status until it reports Completed, then read the signed output URL, which is null until the job finishes and is time limited, so re-poll the request to mint a fresh link if it has expired. Never assume an immediate result. Boomerang allows 60 requests per minute and 600 per hour per key, so pace the per-post calls when a week has a lot of posts, and honor the retry delay on any rate limit response. Merge everything into one list and dedupe by profile, so a person who engaged with three posts appears once. Keep the verbatim comment text and the source post URL attached to each person, because that is the real asset here. A rep needs the exact words and the post they came from, not just a name and an email. Filter the merged list down to people who fit our ideal customer profile on title, seniority, company size, and industry. Drop our own employees and drop known competitors, using the exclusion lists I maintain. Rank whoever is left by intent strength. A substantive comment is the strongest signal: a question, an opinion, a disagreement, or someone describing their own situation. A short or emoji-only comment is the middle tier. A passive reaction is the weakest. Carry that rank through to the CRM records and the digest ordering. Before spending a single credit, check every remaining person against Pipedrive using Search Persons, matching on name plus company. This dedupe step happens BEFORE enrichment, never after. Boomerang holds reserved credits at submit time, so submitting someone who is already in Pipedrive is money burned. Anyone who matches an existing person is pulled out of the enrichment path entirely and routed into the Slack digest under the rep who owns that record. Existing contacts are never silently dropped. Only the genuinely net new people go into a Boomerang Submit Email Finder Enrichment job, sent as a bulk CSV. Poll Get Request Status until it reports Completed, then pull the output CSV from the signed URL. If the job comes back with status Issue, report that in the digest rather than failing silently. For each enriched person that came back with an email, create the record in Pipedrive with Create Person, then create an accompanying Create Lead linked to that person. The lead must carry the verbatim comment text and the source post link, so the rep can open with the thing that person actually said. Put the intent rank on the lead too, and title the lead so it names the person and the post they engaged with. Append every person processed this run to the Google Sheets ledger tab with Append Values: profile URL, name, company, intent rank, whether they were net new or an existing contact, the Pipedrive person and lead ids where applicable, and the run date. This ledger is what guarantees the same engager is never enriched twice. Finish with one Slack Bot Send a Message digest to the sales channel, with two clearly separated sections. First, new leads created, ordered by intent rank, each one quoting the person's comment and linking the post it came from. Second, existing contacts who engaged, grouped by owning rep. Say plainly in the message why that second group matters: an existing contact engaging with our content is a warm signal for an AE working an open deal, not a new-business lead. Close the digest with a short line covering how many posts were processed, how many engagers were skipped as already known, and any posts or enrichment jobs that ended with an issue. ## How to customize - Change the timing or the lookback window. Monday at 8am covering the previous seven days is the default, but a Friday wrap-up works just as well. - Adjust who makes the cut: tighten the ideal customer profile, extend the exclusion lists, or raise the bar so only people who left a comment get looked up and passive reactions are skipped entirely. - Send the digest to each rep as a direct message instead of one shared channel, so everyone sees only their own engagers. ## FAQ ### Will this spend money looking up people we already have in Pipedrive? No, and that is the main point of it. Every person is checked against your CRM before any contact lookup happens. Anyone who already exists is pulled out of the lookup entirely and passed into the Slack digest under the rep who owns them, so you only ever pay for genuinely new people. ### What counts as a strong signal versus a weak one? Someone who wrote a real comment, asked a question, disagreed, or described their own situation is ranked highest, because they told you something you can open a conversation with. A short or emoji-only comment sits in the middle, and a passive reaction sits at the bottom. The digest is ordered so the strongest signals are at the top. ### Why does the digest separate existing contacts into their own section? Because they are a different kind of opportunity. A brand new name is a new-business lead, but an existing contact quietly engaging with your content is a warm signal for whoever is already working that relationship, often while a deal is open. Mixing the two hides the second group, so they get their own section addressed to the owning rep. ### What happens if the same person engages with several posts, or engages again next week? They are only ever handled once. Engagers are combined across all of the week's posts first, and every person processed gets written to a running record in your spreadsheet, which is checked at the start of each run. The same person is never looked up or added twice. ### Do we need to post from a company page for this to work? No. It works from whatever post links your team drops into the spreadsheet tab, whether those are company page posts or personal posts from founders and reps, as long as the post is publicly visible. Use this prompt in General Input: https://www.generalinput.com/prompts/turn-the-people-who-engage-with-your-posts-into-pipedrive-leads