Weekday Slack digest of stalled Dropbox Sign signature requests

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.

Additional information

What does this prompt do?

Pulls every open Dropbox Sign signature request still waiting on a signer and groups them by how long they have been sitting.
Sends a polite reminder to signers in the middle of the stall window so you do not have to chase them by hand.
Calls out the worst offenders, requests that are about to expire or have already been nudged, as deals at risk so a human can decide whether to cancel.
Posts one consolidated Slack message each weekday morning so the whole team sees the same picture without digging through email.

What do I need to use this?

A Dropbox Sign account with permission to view and remind on signature requests.
A Slack workspace and the channel you want the morning digest posted to.
A rough idea of when a request counts as stalled for your team (the defaults are 3 to 6 days for a nudge and 7 plus days for escalation).

How can I customize it?

Change the schedule, for example move the digest to 8am, run it twice a day, or skip Mondays.
Tune the age buckets and escalation rules to match your sales cycle, like nudging at day 2 instead of day 3, or escalating anything past 5 days.
Pick the Slack channel and tone of the digest, and decide whether to also tag the deal owner for at-risk requests.

Frequently asked questions

Does this replace the automatic reminders Dropbox Sign already sends?

No. Dropbox Sign's built-in reminders still fire on their own schedule. This workflow adds a higher-signal weekday digest and a judgement layer about when to escalate, on top of those built-in nudges.

Will it cancel deals automatically?

No. Cancelling is intentionally left to a human. The agent surfaces the requests that look dead so you can decide, rather than killing anything on its own.

How does the agent decide what is a reminder vs a deals-at-risk callout?

Requests sitting 3 to 6 days get a gentle reminder. Requests 7 or more days old, requests already reminded multiple times, or requests close to their expiration get pulled into the deals-at-risk section for human review.

Can I send the digest somewhere other than Slack?

Yes. The same prompt works if you swap Slack for email, Microsoft Teams, or any messaging tool you already connect. Just tell the workflow author where to post it.

What happens on holidays or if Slack is down?

The schedule runs every weekday, so holidays will still send unless you adjust the cron. If Slack fails for a run, the next run will pick up the current state of the signature requests, so nothing gets permanently missed.