Weekday digest of stalled Dropbox Sign requests

By General Input

Every weekday at 9am, get a Slack digest of signature requests gone quiet, with smart reminders and a deals-at-risk callout for the worst offenders.

Integrations

  • Dropbox Sign
  • Slack Bot

Type

Agentic Task

Categories

  • Sales
  • Operations

Build me an agent-style workflow that runs on a cron trigger every weekday at 9am US Eastern Time and chases down stalled Dropbox Sign signature requests.

On each run, the agent should use the Dropbox Sign List Signature Requests operation to fetch every signature request that is still incomplete and waiting on at least one signer. It should page through results until it has them all, and ignore anything already complete, declined, or cancelled.

Then it needs to group those open requests into three buckets based on age and risk: (1) fresh, sent in the last 2 days, which it should leave alone, (2) moderately stale, sent 3 to 6 days ago with no signer activity, and (3) at risk, which means sent 7 or more days ago, or already reminded multiple times, or within 3 days of expiration. The bucketing is the whole point of using an agent here, so the agent should reason about each request rather than apply a blind rule, and lean on signer-level status from the request so it does not nudge people who already signed.

For every request in the moderately stale bucket, the agent should call Send Signature Request Reminder on the still-pending signer to ping them. It should not remind signers who already signed, and it should not send more than one reminder per signer per run.

For the at-risk bucket, do not auto-cancel anything. Instead, include those requests in a clearly labelled "deals at risk" section of the digest so a human can decide whether to follow up personally or use Cancel Signature Request to close it out. Also list any requests where every signer has gone completely cold (no opens, no views) as a separate "gone cold" section.

Finally, post one consolidated digest message to Slack using the Slack Bot Send a Message operation. The channel should be configurable, defaulting to something like #deals or #revops. The message should be a single readable post with sections for: requests reminded today (title, signer name and email, days outstanding), deals at risk (same fields plus reason it landed in at-risk), and gone cold signers. If there is nothing to report in a section, omit that section rather than printing an empty header. Keep the formatting Slack-friendly using mrkdwn.

If the agent finds zero stalled requests at all, it should still post a short "all clear" message so the team knows the workflow ran.

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 opensLiveKit 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 seatsPause marketing emails to escalated customers, then restore them