We're launching AI agents for business operations, with a developer API. Read the announcement
All templates
For engineering teams, DevOps engineers & product managers

Send your team a daily deploy and release digest

Every morning, WebRun opens GitHub to list overnight merges to main and release tags, cross-references Datadog for any deploy events, and posts a formatted digest to Slack so your whole team knows what is live.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 8:00 AM WebRun
1 GitHub collect overnight merges and release tags
2 Datadog verify deploy events
3 Slack post the morning deploy digest
Run a sample
Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens github.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    GitHub - collect overnight merges and release tags
    github.com How to Automate GitHub
    WebRun in GitHub: collect overnight merges and release tags
    WebRun opens GitHub to collect overnight merges and release tags.
    • Open your repository's Releases page and note any new tags since yesterday
    • Check the Commits tab on main for merges after the previous digest
    • Capture the PR title, author, merge time, and release notes for each

    Done when All overnight releases and significant merges are listed with their metadata.

  3. 2
    Datadog - verify deploy events
    datadoghq.com How to Automate Datadog
    WebRun in Datadog: verify deploy events
    WebRun opens Datadog to verify deploy events.
    • Open Datadog Events and filter to deployment events from the past 24 hours
    • Match each event to the GitHub release or merge to confirm successful promotion
    • Note any failed or rolled-back deploys for prominent flagging

    Done when Each deploy has a confirmed status (success, failed, or rolled back).

  4. 3
    Slack - post the morning deploy digest
    slack.com How to Automate Slack
    WebRun in Slack: post the morning deploy digest
    WebRun opens Slack to post the morning deploy digest.
    • Post a structured digest to #deployments: one line per release with version, author, and status
    • Flag any failed deploys in red at the top of the message

    Done when The team has this morning's complete deploy summary in Slack.

How can I automatically send my team a daily deploy and release digest?

Every morning, WebRun opens GitHub to list overnight merges to main and release tags, cross-references Datadog for deploy events, and posts a formatted digest to Slack - so your whole team knows what is live without checking multiple tools or waiting for a standup.

  • Every overnight deploy surfaced in Slack before standup
  • Team aligned on what is live without manual release comms
  • No missed version bumps or release notes from overnight activity

Built for engineering teams · DevOps engineers · product managers · engineering managers

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
github.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Deploy digest · Slack
OutputWhat each run produces - A formatted list of every overnight deploy with version, author, status, and a link to the GitHub release.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it cover all our repositories?

It covers whichever repos you add to the plan - add as many as you like and they all appear in the same morning digest.

What if there were no deploys overnight?

It posts a brief 'Nothing shipped last night' message so the team can confirm the silence was intentional.

Can it trigger a rollback if a deploy fails?

No - rollbacks change production and require a human decision. WebRun flags the failure prominently; you initiate the rollback.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.