Daily triage of stalled PandaDoc deals into Slack

Build an agent workflow that runs every weekday at 9am Eastern (cron trigger) and triages stalled PandaDoc documents. The point is per-document judgment, which is why this is an agent and not a fixed pipeline.

Step 1. Find stuck documents. Use PandaDoc List Documents filtered to status sent or viewed, where the last status change is more than three days ago. Skip anything sent in the last 48 hours.

Step 2. For each stuck document, gather context. Call PandaDoc Get Document Details for recipients and metadata, and PandaDoc List Document Audit Trail to see who has viewed, who hasn't, and how many times.

Step 3. Pull revenue context from HubSpot. Use PandaDoc List Linked Objects for Document to find the linked HubSpot deal, then call HubSpot Get Deal to read the deal amount and owner. If a document has no linked deal, mark its revenue-at-risk as unknown and continue.

Step 4. Decide per document. The agent picks one bucket: (a) recipient has not opened the document in five or more days, fire PandaDoc Send Manual Reminder with a short, tailored nudge referencing the document name; (b) recipient has opened multiple times without signing, or the linked deal amount is high-value (default threshold: top 20 percent of open deals, or $25,000 if there is no clear distribution), do not auto-nudge, instead flag it for the deal owner to handle personally; (c) bottleneck is internal (the last open action was by someone on our team, or a recipient on our domain still needs to act), skip it. Always skip docs sent in the last 48 hours.

Step 5. Post one Slack digest using Slack Send a Message to a channel called #pipeline-hygiene (let the user override the channel at setup). The digest should include: a one-line headline with the total dollars at risk and the count of docs in each bucket; a table or list of every stuck document with the document name, the linked deal name and amount, the recipient, the bucket the agent put it in, and the action taken (reminder sent / escalated to <owner> / skipped because <reason>). For the escalation bucket, @-mention the deal owner in the Slack message if their Slack handle is known.

Tone: the manual reminder copy should be short, polite, and reference the document by name. The Slack digest should be scannable for a sales leader skimming on a phone at 9am. Do not send any reminder if it would be the second nudge in the same week for the same recipient.