Score new Pipedrive leads and alert Slack on high-fit ones

When a new lead lands in Pipedrive, an agent pulls prior deals and notes, writes a fit assessment to the lead, and pings Slack only when it's worth a rep's time.

Agentic Task
PipedriveSlack BotSalesLead EnrichmentNotifications & Alerts
PromptCreate

Build me an agent workflow that triages every new lead in Pipedrive, writes a context-rich assessment back to the lead, and only pages Slack when the lead is worth a rep's attention.

Trigger: an incoming webhook from Pipedrive on the create.lead event. During setup, I'll create the outgoing webhook in Pipedrive pointing at the workflow URL. The payload will include the new lead's ID (a UUID).

When the webhook fires, the agent should:

1. Call Pipedrive's Get Lead with the lead ID to load the full lead, including title, value, currency, owner, attached person ID, attached organization ID, source channel, and labels.

2. If the lead has a linked person, call Pipedrive's Get Person to load contact details (name, job title, emails, phones, custom fields).

3. If the lead has a linked organization, call Pipedrive's Get Organization to load org details (name, address, owner, and any useful custom fields like industry or size).

4. Call Pipedrive's List Deals filtered by the linked person ID, and again filtered by the linked organization ID, to surface every prior and currently open deal tied to this contact or company. For each deal, capture status (open, won, lost), value, pipeline and stage, and close date.

5. Call Pipedrive's List Notes filtered by the same person and organization to surface prior conversation context and any open threads the team has already started.

6. Synthesize everything into a short, plain-language assessment of around 4 to 6 sentences that covers: whether this looks like a net-new contact, a repeat lead, or an existing customer; notable prior deals (won, lost, open) and what they imply; a simple fit and priority read of high, medium, or low with one reason; and the single most useful next step for the rep.

7. Use Pipedrive's Create Note to attach that assessment to the lead so it lives on the record. Do this for every lead, including low-fit ones, so we always have a record-keeping trail. The note content field accepts HTML, so wrap the summary in simple paragraph tags.

8. If and only if the assessment is high-fit, use Slack Bot's Send a Message to post to our lead-routing channel (let me pick the channel during setup). The message should tag the lead owner by name, include a one-line headline like 'High-fit lead: <Organization> — <Person>, <role>', include the assessment paragraph inline, and link back to the lead in Pipedrive so the rep can click through.

Do not post to Slack for medium or low-fit leads. The Pipedrive note still gets written either way. Reps should only see what is worth their time in the channel.

Handle missing data gracefully. If a lead has no person or no organization attached, skip those lookups, note it explicitly in the assessment, and still produce a usable fit read and next step from what is available.

What does this prompt do?

  • Watches Pipedrive for new leads and reacts the moment one is created.
  • Pulls the contact's prior deals, organization history, and open conversation notes from your Pipedrive.
  • Writes a one-paragraph fit and priority read directly to the lead so the context lives on the CRM record.
  • Pings your sales Slack channel and tags the assigned owner only when the lead looks worth a rep's attention.

What do I need to use this?

  • A Pipedrive account on a plan that allows outgoing webhooks, with permission to create them.
  • A Slack workspace and the channel you want high-fit lead alerts to land in.
  • A loose sense of what a high-fit lead looks like for you (industry, deal size, repeat contact, target accounts).

How can I customize it?

  • Change what counts as high-fit, for example existing customers, target industries, or a minimum deal value.
  • Post to a different Slack channel, or DM the assigned rep directly instead of broadcasting.
  • Adjust the tone or length of the summary that gets pinned to the lead in Pipedrive.

FAQs

Will this notify Slack for every single new lead?
No. Every new lead gets a written assessment saved to its Pipedrive record, but Slack only fires when the agent decides the lead is high-fit. Low and medium-fit leads stay quiet so your sales channel does not become noise.
What happens to low-fit leads?
They still get the one-paragraph assessment attached to the lead in Pipedrive as a note, so you have a full record-keeping trail and can revisit them later. They just do not page anyone in Slack.
Does this need a third-party data enrichment tool?
No. The agent uses what Pipedrive already knows about the contact and organization, including their prior deals, won and lost history, and any notes your team has filed. That history is usually high-signal on its own for prioritizing and routing.
What if a new lead has no person or organization attached yet?
The agent handles that gracefully. It skips the lookups it cannot do, calls that out in the summary, and still produces a useful read and routing decision based on what is available.
Can I send the alert to a private Slack channel?
Yes. You can route the message to any channel the Slack bot is a member of, including private channels. You pick the channel during setup.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task
Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.

Amazon SQS
GitHub
Slack Bot
Agentic Task

Stop sizing up every new Pipedrive lead by hand.

Connect Pipedrive and Slack once, and Geni triages every new lead the moment it hits your CRM.