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

By General Input

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.

Integrations

  • Pipedrive
  • Slack Bot

Type

Agentic Task

Categories

  • Sales

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.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensStop cold emails to anyone with a live deal in PipedriveLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seats