Automated Mediafly Content Usage Digest
Every morning, WebRun opens Mediafly, pulls yesterday's content shares and buyer engagement, such as which decks were opened and how long buyers spent on them, groups the totals by asset, and posts a summary to Slack, mirrored to Telegram, so sales enablement can see what content is actually landing.
How do I see which sales content is actually getting used?
WebRun checks Mediafly every morning for content shared and opened the day before, capturing which asset each rep sent and how much time buyers spent on it. It groups the totals by asset and posts a summary to Slack, mirrored to Telegram, so sales enablement can see what content is actually landing with buyers.
- Enablement sees which content is landing every morning, not at quarter review
- Low engagement assets get surfaced instead of staying hidden in the library
- The library itself is never changed automatically
Built for sales enablement teams · content marketing · revenue operations · product marketing
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
mediafly.comin a real browser with your saved login - no setup, no API keys. -
1
Mediafly - pull yesterday's content shares and opens
mediafly.com
WebRun opens Mediafly to pull yesterday's content shares and opens. - Open Mediafly and check content shared and opened since the last check
- Capture which asset, which rep shared it, and buyer engagement like opens and time spent
- Group the totals by asset
Done when Yesterday's content activity is captured and grouped by asset.
-
2
Slack - post the digest to enablement
slack.com
WebRun opens Slack to post the digest to enablement. - Post the daily digest to the enablement channel: top assets by engagement and total shares
- Call out any asset with unusually high or low engagement
Done when Enablement has today's content usage digest in Slack.
-
3
Telegram - mirror the digest to Telegram
telegram.org
WebRun opens Telegram to mirror the digest to Telegram. - Mirror the same digest to the enablement Telegram channel
- Keep the format identical to the Slack post
Done when The digest is posted in both Slack and 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 change or remove any content from the library?
No. WebRun only reports on how existing content was shared and viewed. Managing the content library stays with your enablement team.
What counts as buyer engagement here?
Whether a shared asset was opened and how much time a buyer spent on it, as tracked by Mediafly. It reflects what buyers actually did, not just what was sent.
Why is the digest posted to both Slack and Telegram?
So enablement and sales leadership see it regardless of which app they check first. Both copies carry the same information.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.