Stale deal nudger
By Toolspoke
Finds open Pipedrive deals that have gone quiet and posts one Slack message, by owner, with a next step for each.
Needs a Toolspoke account. You choose which project it installs into.
- Pipedrive + Slack
- Required integrations
- Runs on a schedule
- Weekdays at 9am by default
- Post one message
- What its last step does
- Nothing destructive
- 0 of 25 actions in its tools
On this page
The short version
- What it is
- A ready-made Toolspoke agent that finds Pipedrive deals that have gone quiet and suggests a next step for each.
- What it reads
- Open deals, their stage and owner, and the activities logged and booked against each.
- Where it posts
- One Slack channel, grouped by deal owner.
- What it flags
- Open deals with no activity in 14 days, or a different limit you set per stage, and nothing booked.
- How often
- Weekdays at 9am once you switch it on. If nothing is stale it posts nothing.
- What it never does
- Create an activity, a note or a deal, or change a deal's stage.
- What you need
- A Toolspoke account, a Pipedrive API token and a Slack workspace.
What Stale deal nudger does
Stale deal nudger is an AI agent that reads your open Pipedrive deals each weekday, finds the ones with no recent activity and nothing booked, and posts them to Slack by owner with one concrete next step for each.
A deal rarely dies in one moment. It goes quiet: the proposal went out, nobody followed up, and three weeks later the buyer has chosen someone else.
Pipedrive marks rotting deals in red, but only for people who open the pipeline view, and the red does not say what to do next.
Stale deal nudger checks each open deal's last done activity and whether anything is booked. If the deal has been quiet longer than the limit for its stage, it suggests one next step based on where the deal is and what happened last, and posts the list to the team's channel.
In practice, each weekday morning you get:
- Open deals with no activity for 14 days and nothing booked
- A different limit per stage, if you set one
- One specific next step for each deal
- Silence when nothing is stale
How it works
Stale deal nudger works in four steps each weekday morning: it reads the pipeline, finds each deal's last activity, decides what is stale and posts a list by owner. All of it comes from the agent's written instructions, which you can read and edit after you install it.
Step 1: Find open deals
It collects deals from recent activities and the search terms you chose.
Step 2: Read the last touch
It reads each deal's latest done activity and anything booked.
Step 3: Decide and suggest
It flags deals past their stage's limit and suggests one next step.
Step 4: Post by owner
It posts one message, grouped by owner, most quiet first.
How it finds your deals
Pipedrive's deal search needs a search term, and the connector has no action that lists every deal. So the agent collects deal ids from each owner's activities over the last 180 days with list_activities, adds deals from search_deals for the terms you chose at install, and reads each with get_deal. A deal with no activity ever that matches no term can be missed, and the post says how deals were found.
It knows what is booked
A deal with a call booked for Friday is not stale, however long ago the last one was. The agent checks each deal's activities for anything outstanding in the future and leaves those deals out.
It uses a limit per stage
Fourteen days is the default. You can set others: a proposal that has had no follow-up for a week matters more than a lead that is still being qualified.
It suggests and stops
It never books the call or writes the note. The owner does. The limits are under what it will never do.
What a morning list looks like
A message from Stale deal nudger is one Slack post, grouped by owner. Within each owner, the deal quiet longest comes first.
Fernhill
Channels
- # sales
- # deals
- # marketing
- # general
# sales
Tuesday. 38 open deals read, 5 stale. Limit 14 days, 7 for Proposal sent.
Maya Chen (2)
- Fernhill Studio, 8,400, Proposal sent. Quiet 19 days, last activity: proposal emailed. Next: follow up on the proposal and ask for a decision date.
- Aldgate Clinics, 26,000, Negotiation. Quiet 16 days, last activity: pricing call. Next: ask who else signs off and when they meet.
Jonas Berg (1)
- Pebble & Co, 3,200, Proposal sent. Quiet 9 days, last activity: demo. Next: send the proposal summary with two dates for a call.
The rest
2 more stale deals listed at the end of the message. Deals found through activities and the terms set at install.
- Quiet for weeks
Deals well past their limit, usually late in the pipeline, where silence costs the most.
- Past the stage limit
Deals over a shorter limit you set for their stage, caught before they go cold.
- The rest
Further stale deals, and a note on how deals were found, so a missing one can be explained.
Why it sometimes says nothing
If no deal is stale, Stale deal nudger posts nothing. A daily all clear teaches people to skip the channel.
A failed run is different. If Pipedrive cannot be read, it posts that once, so a quiet morning is not mistaken for a healthy pipeline.
Who uses Stale deal nudger
Stale deal nudger suits small sales teams that run their pipeline in Pipedrive and talk in Slack. The examples use made-up names.
A rep with a long pipeline
Maya Chen carries thirty deals. The list tells her which proposals she has not chased, and what to say.
A sales lead coaching the team
Jonas Berg reads the list before standup and knows which deals to ask about.
A founder who sells part time
Ruth Alvarez sells between other work. The morning message is her reminder to follow up.
An agency winning new work
Oskar Lind's agency runs a short pipeline with long silences. A seven day limit on proposals keeps them moving.
What Stale deal nudger connects to
Stale deal nudger connects to two tools: it reads Pipedrive and posts to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.
Pipedrive
RequiredSearch and update deals, people, organizations, activities and notes in the Pipedrive CRM.
Authentication: API token
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
| Tool | What Stale deal nudger does | What it cannot do |
|---|---|---|
| Pipedrive | Reads deals, activities, stages and users (search_deals, get_deal, list_activities, list_stages, list_users). | Delete a deal: the connector has no delete action. It can create deals, people and activities, add notes and update deals, which this agent's instructions forbid. |
| Slack | Posts one message with send_message, to a channel. | Delete messages: the connector has no delete action. |
The Pipedrive connection can create activities, notes and deals and change a deal's stage. Stale deal nudger is told never to. That is an instruction, not a lock. To enforce it, switch create_deal, update_deal, create_person, create_activity and add_note off in your project. The access control guide explains how.
The activity log records each call. Pipedrive activity reads keep only that the call happened. The message posted to Slack is stored.
What Stale deal nudger will never do
Stale deal nudger is told never to create an activity, a note, a deal or a person, and never to change a deal's stage, value, owner or status. It suggests, and the owner acts.
- Create an activity, a note, a deal or a person.
- Change a deal's stage, value, owner or status, or mark it won or lost.
- Post to an owner directly.
- Suggest a next step that needs information you do not have, such as a discount or a price.
Why it does not book the follow-up
An activity booked by an agent looks like a promise the rep made. It fills calendars with calls nobody planned and makes the pipeline look busier than it is. The suggestion stays a suggestion until the owner books it.
Why it gives one step, not a script
The owner knows the buyer. The agent gives one specific next step from the stage and the last activity, and never invents a discount or a price it does not have.
Why you may still want a lock
Every limit here is an instruction. Switching the write actions off in your project makes the Pipedrive connection read-only for this agent.
If something goes wrong
If Pipedrive cannot be read, post that once and stop. A deal with no activities and not matching any search term cannot be found this way: say in the post that deals are found through activities and the chosen terms, so a person knows to widen the terms if one is missing.
These are written into Stale deal nudger's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
Stale deal nudger reads your pipeline and points at what has gone quiet. Every call, note and stage change stays with the owner.
When Stale deal nudger runs
Stale deal nudger runs on weekdays at 9am, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.
- Each run reads the open deals and their activities.
- A deal with something booked is never flagged.
- When nothing is stale, it posts nothing.
- If Pipedrive cannot be read, it posts that once.
Each run uses model credit from your workspace balance, even when nothing is posted, so it makes five runs a week. The Pipedrive and Slack calls themselves are free.
Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the days and time and edit its instructions. The agent's page lists recent runs and their cost.
How to set up Stale deal nudger
To catch quiet deals each morning, add Stale deal nudger to a Toolspoke project, connect Pipedrive and Slack, set your limits and switch on the schedule. Nothing runs until the last step.
Step 1: Create a Toolspoke account or sign in
Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.
Step 2: Add it to a project
Pick the project it should live in. You get your own editable copy, and you can see the two tools it brings before anything connects.
Step 3: Connect Pipedrive
Copy your personal API token from Pipedrive and paste it. It is stored encrypted and the agent never sees it.
Step 4: Connect Slack
Choose Sign in with Slack and approve the Toolspoke app. For a private channel, add the Toolspoke bot to it first.
Step 5: Set limits and search terms
Name the channel, the days that make a deal stale and any different limit per stage. Add a few search terms that cover your deal titles, so deals with no activity at all are found too.
Step 6: Switch on the schedule
The schedule arrives switched off. Run it once to see a list, then switch it on.
Make Stale deal nudger fit your pipeline
Stale deal nudger's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.
Paste any sentence below into the builder chat, or say the same thing in your own words.
Treat a deal in Negotiation as stale after 5 days.
Leave out deals worth less than 1,000.
Mention each owner by their Slack name above their deals.
Only check deals in the New business pipeline.
Run on Mondays at 9am only.
This changes when the agent wakes up, so the builder edits its schedule, not the instructions.
None of these edits needs more access or touches the Never rules. They change what Stale deal nudger is told, not what the connections allow.
How it compares to other options
Stale deal nudger beats the alternatives when you want quiet deals pushed into Slack with a next step, and loses to them when you want the reminder to live inside Pipedrive.
| Compared on | Stale deal nudger | Pipedrive's rotting deals | A Pipedrive automation | Checking the pipeline yourself |
|---|---|---|---|---|
| Arrives without opening Pipedrive | Yes, in Slack | No | Depends on the action | No |
| A different limit per stage | Yes | Yes | If you build it | In your head |
| Ignores deals with something booked | Yes | No | If you build it | Yes |
| Suggests a next step | Yes, one per deal | No | A fixed one | Yes |
| Books activities for you | Told not to | No | Often, by design | Up to you |
| Sees every deal | Through activities and terms | Yes | Yes | Yes |
| Setup effort | Connect two accounts | A setting per stage | Build each rule | Every morning |
Pipedrive's rotting deals setting is the better choice when your team works in the pipeline view all day. It sees every deal and needs no connection.
A Pipedrive automation is better when you want a follow-up activity created on every deal that crosses a limit. This agent deliberately leaves that to the owner.
Frequently asked questions
Can Stale deal nudger book activities or change a deal?
The Pipedrive connection can, and the agent is told never to. To enforce it, switch create_activity, add_note, create_deal, create_person and update_deal off in your project (how access works).
Will it find every open deal?
Pipedrive's deal search needs a search term, so the agent finds deals through each owner's activities over the last 180 days and the search terms you set at install. A deal with no activity ever that matches no term can be missed. Add terms that cover your deal titles to close that gap.
What counts as stale?
An open deal whose last done activity is older than the limit for its stage, 14 days by default, with nothing booked in the future.
Can I set a different limit per stage?
Yes. Name the stage and the number of days at install, or ask the builder later.
Does it message owners directly?
No. It posts one message to one channel, grouped by owner.
Where do the next steps come from?
From the deal's stage and its last activity. They are suggestions, one sentence each, and never include a price or discount.
Is Stale deal nudger free?
It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.
Catch a deal before it goes cold
Connect Pipedrive and Slack, set your limits and switch on the schedule. Your first list lands at 9am on the next weekday.