All templates

Automated Countly App Usage and Crash Digest

Every morning, WebRun opens Countly, reads yesterday's active users, session counts, and crash reports, opens a Trello card for any new crash spike, and posts the full digest to Microsoft Teams.

Runs on WebRun · Strict Lockdown policy
Every day at 7:00 AM WebRunorchestrates each step
1 Countly read usage and crash data
2 Trello flag new crash spikes
3 Microsoft Teams post the digest
In short

How do I get a daily Countly usage and crash digest?

WebRun reads your Countly active users, sessions, and crash reports every morning, opens a Trello card for any crash type that spiked above normal, and posts the full digest to Microsoft Teams. Product and mobile engineering teams catch a new crash spike the same morning instead of finding it in a support queue.

  • A new crash spike is flagged the same morning it starts
  • Usage and crash data land in Teams without opening Countly
  • Only genuine spikes generate a tracked card

Built for product managers · mobile engineering teams · app development teams

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 count.ly in a real browser with your saved login - no setup, no API keys.

  2. 1
    Countly - read usage and crash data
    • Open Countly and check yesterday's active users and sessions
    • Read the crash report summary
    • Compare crash counts against the recent average

    Done when Yesterday's usage and crash data is read and compared.

  3. 2
    Trello - flag new crash spikes
    trello.com
    WebRun in Trello: flag new crash spikes
    WebRun opens Trello to flag new crash spikes.
    • Open the mobile engineering board in Trello
    • Create a card for any crash type that spiked above normal
    • Note the affected app version and crash count

    Done when Any new crash spike has a tracked card.

  4. 3
    Microsoft Teams - post the digest
    microsoft.com
    WebRun in Microsoft Teams: post the digest
    WebRun opens Microsoft Teams to post the digest.
    • Open the product channel in Microsoft Teams
    • Post yesterday's active users, sessions, and crash summary
    • Link to the Trello card for any new spike

    Done when The team has yesterday's usage digest in Teams.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
count.ly
ScheduleRuns automatically on this cadence
Every day at 7:00 AM
DeliveryHow each run's result reaches you
Usage digest · Microsoft Teams
OutputWhat each run produces - A daily usage and crash digest, with a Trello card for any new crash spike.
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 WebRun fix the crash or push an update?

No. It only reads usage and crash data from Countly. Fixing the underlying bug or shipping a release stays an engineering task.

How is a crash spike identified?

By comparing yesterday's crash count for each type against its recent average. Only a genuine spike gets a Trello card.

Does it see individual user data?

No. It only reads aggregate usage and crash counts, the same summary numbers Countly already reports.

Put this on autopilot.

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