Automated Signaturely Daily Status Digest
Every morning, WebRun opens Signaturely, checks the status of every document sent for signature, posts a digest of what's signed and what's still pending to Slack, and sends a separate Telegram alert right away for anything marked declined.
How do I get a daily digest of Signaturely status updates?
WebRun checks Signaturely every morning for the status of every document sent for signature, posts a digest of what's signed and pending to Slack, and sends an immediate Telegram alert for anything declined. Routine status updates land in a daily digest while declines reach you the same day they happen.
- Signed and pending documents land in Slack every morning
- Declines reach you the same day instead of the next digest
- No one has to open Signaturely just to check status
Built for freelancers · small businesses · HR teams · sales teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.signaturely.comin a real browser with your saved login - no setup, no API keys. -
1
Signaturely - check every document's status
signaturely.com
WebRun opens Signaturely to check every document's status. - Open Signaturely and list documents sent for signature
- Read the current status of each
- Separate signed and pending documents from any declined
Done when Every document's status has been read and sorted.
-
2
Slack - post the daily digest
slack.com
WebRun opens Slack to post the daily digest. - Post the day's signed and pending documents to Slack
- Group them by client or project
- Include how long each pending document has been waiting
Done when The team has today's status digest in Slack.
-
3
Telegram - alert on declines
telegram.org
WebRun opens Telegram to alert on declines. - Send a Telegram alert for any document marked declined
- Include the signer and the document name
- Skip the alert if nothing was declined
Done when Any decline since the last run has been alerted in Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it send anything for signature itself?
No. WebRun only reads the status of documents already sent through Signaturely. It never creates or sends a new document for signature.
Why does a decline get a separate alert?
A decline usually needs a quick response, so it gets an immediate Telegram alert rather than waiting for the next morning's Slack digest.
Will it contact the signer?
No. It only posts to your own Slack and Telegram. It never emails or messages the person signing the document.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.