Salesforce opportunity hygiene reminders via Slack

Starting promptUse this prompt as a starting point to build your workflow.

Build a workflow that keeps Salesforce opportunity pipeline hygiene high by gently nudging opportunity owners in a chat tool to update stale open opportunities, and lets them fix the issues without leaving that chat tool, their updates should write straight back to Salesforce. Trigger it on a schedule that runs a couple of times a week (e.g. twice-weekly, weekday morning). The scheduled run should scan open opportunities in Salesforce (scoped to the deal types that matter, e.g. new business and expansions) and evaluate each against a set of "staleness" rules. For example: the close date has already passed, there's no next step defined once a deal reaches a later stage, a next step hasn't been refreshed in a while, a deal has sat in the same stage too long, there's been no recent activity, or the close date is imminent while the deal is still early. Make the rules and their thresholds easy to find and adjust in one place. Keep noise low: group the findings so each owner gets a single digest rather than one message per opportunity, skip anything an owner has snoozed, and skip owners you can't match to a chat account. In the digest, give each flagged opportunity inline controls so the owner can act right there, fill in or refresh the next step, change the stage, set a new close date, or snooze the nudge for a period. When they act, apply the change back to Salesforce immediately and confirm it in the chat. To receive those interactions, expose a webhook endpoint that your chat tool calls when a user clicks a button, picks from a dropdown, or submits a form, then have a step apply the corresponding Salesforce update (or record the snooze) and post a confirmation. Persist snoozes in durable storage so the next scan honors them. Use Salesforce for reading opportunities and writing updates (via its REST API), and post/receive the nudges through Slack — or your team's chat tool (Microsoft Teams, Google Chat, etc.). Frame both as swappable: any CRM with an API and any chat platform that supports interactive messages and a webhook callback would work. Keep this high-level — don't hardcode specific field names or exact query shapes; those belong in the build. Tools used: Salesforce, Slack

New to Tines?Sign up free for Tines 3B Explore Edition

What this prompt builds

A scheduled workflow that scans Salesforce for stale opportunities against configurable hygiene rules, groups findings by owner, and sends a single Slack digest with inline controls to update next steps, stages, or close dates directly back to Salesforce. Each action triggers a webhook that applies the change in real time and confirms it in chat, while snoozes are persisted to reduce noise on subsequent runs. Designed to improve pipeline hygiene and velocity without adding dashboards or overwhelming sales reps.

The problem

Sales opportunities become stale and slip through the cracks when close dates pass, next steps go undefined, or deals sit too long in a single stage, but RevOps teams don't want to add yet another dashboard or flood reps with alerts. Teams need a way to surface hygiene issues and make it trivial for reps to fix them, ideally without leaving the tools they're already in. This workflow scans open Salesforce opportunities against a set of configurable staleness rules (overdue close dates, missing next steps, inactive deals, etc.), then sends each owner a single grouped digest in Slack with inline controls to update the next step, change the stage, adjust the close date, or snooze the reminder — every action writes straight back to Salesforce in real time.

Solution and impact

Reps stay on top of pipeline hygiene without context-switching or dashboard fatigue: they receive a consolidated Slack message for all their flagged opportunities and can take action (update fields, change stages, set dates, or snooze) with a single click or form submission that syncs immediately to Salesforce. RevOps teams maintain clean, accurate pipeline data and higher velocity without manual follow-up or overwhelming alerts. The workflow's staleness rules and thresholds live in one place for easy tuning, and snooze state persists across runs to keep noise low and respect each rep's workflow.