How we handle GDPR data-subject requests on a deadline
Legal
The pipeline-hygiene agent we run on Kortix — it scans HubSpot every day for stale deals, missing next steps, deals stalled in a stage, and overdue tasks, nudges the owning rep in Slack, and escalates the worst offenders to their manager.
A pipeline decays quietly. A deal goes a week without a call or an email and nobody notices. A rep forecasts a close date and never sets one. A deal sits in "Proposal Sent" for a month past when it should have moved. A follow-up task comes due and slides by unflagged. None of this shows up in a stage-by-stage pipeline report — the deal is still "open," still counted, still apparently fine.
We run a pipeline-hygiene agent on Kortix that reads HubSpot every day and flags exactly this: deals gone quiet, missing next steps and close dates, deals stuck in their current stage, and tasks past due. It nudges the owning rep in Slack and escalates the worst of the day to their manager. It is read-mostly — it flags and it nudges, and it never touches a deal's stage, owner, or amount.
This is a different problem than dirty CRM data. Duplicate contacts and missing job titles are a data-quality issue; a deal that hasn't moved in three weeks is a process issue — the pipeline itself is not doing what it's supposed to do, which is progress toward a close. A stage-by-stage pipeline report can't tell the difference between a deal that's actively advancing and one that's been quietly parked, because both show up the same way: "open," sitting in a stage, counting toward the forecast.
The usual fix is the weekly pipeline review, where a manager scrolls every open deal looking for the ones that have gone stale. By the time that meeting happens, a deal that went quiet on Monday has already lost a week, and the review only catches what someone remembers to ask about. Reps are heads-down selling, not auditing their own deal hygiene, and a next-step field or a close date left blank rarely gets attention until forecast time, when it's too late to fix cheaply.
A daily cron triggers an agent that spawns a fresh, isolated session with read-mostly access to HubSpot. It pulls every open deal, checks it against four hygiene rules — no logged activity in the configured window, a missing next step or close date, no stage movement past the configured window, and any overdue task tied to the deal — and flags what it finds. It nudges each owning rep in Slack with exactly what needs attention on their deals, and separately escalates the day's worst offenders to the sales manager's channel. It never changes a deal's stage, reassigns its owner, or edits its amount.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the pipeline-hygiene-rules skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily pipeline-hygiene agent in this workspace.
Create the agent agents/pipeline-hygiene.md. Its job is to find open HubSpot deals that need attention and nudge their owners. It may use the HubSpot and Slack connectors.
Create the skill skills/pipeline-hygiene-rules/SKILL.md with these rules:
Add a cron trigger daily-pipeline-hygiene-scan to kortix.yaml. It runs the pipeline-hygiene agent every day at 06:00 with the prompt "Load the pipeline-hygiene-rules skill and run one complete pipeline-hygiene scan."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your CRM and Slack. Credentials are brokered server-side and never enter the agent's machine.
Reads open deals and tasks, and sets the hygiene flag.
Nudges each owning rep and escalates the worst deals.
Merge the change request, then start a session with the pipeline-hygiene agent and send this prompt. Check the flags and the nudges before you let the schedule take over.
Run one pipeline-hygiene scan on HubSpot.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 06:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: daily-pipeline-hygiene-scan name: Daily pipeline-hygiene scan on: cron: "0 0 6 * * *" run: agent: pipeline-hygiene prompt: Load the pipeline-hygiene-rules skill and run one complete pipeline-hygiene scan.The agent reads deals, activities and tasks. The only field it writes is the hygiene flag. It never moves a stage, reassigns an owner, edits an amount, logs an activity or closes a task. The rep and the sales manager decide what happens to each deal.
Each run ends with one nudge per rep and one escalation in the managers' channel. This is what a run looks like in the session:
Scanned 184 open deals and flagged 23. 11 are stale, 7 have no next step or close date, 4 are stalled and 5 have overdue tasks. Sent nudges to 9 reps and escalated the top 5 deals to #sales-management.
Once it works, paste any of these into the same session.
Every Monday, post to #sales-management how many deals tripped each rule in each of the last 4 weeks.
The day before each forecast call, list every deal in the Commit forecast category that has a hygiene flag, and send the list to each owner.
Keep a list in memory of reps who are out of office, and send their nudges to their manager until they are back.
Reading and flagging every open deal every day is a trust question, so the agent's access is narrow and one-directional in the ways that matter:
The deals that used to sit quietly until the next pipeline review now surface the same day they go stale, with a nudge to the rep who owns them and an escalation for the ones a manager should already be watching. The agent only flags and nudges; the rep and the manager still decide what moves.