Automation Composer

Build an automation. Know when not to send it.

Reports and alerts used to be somebody's morning. This builds one from a rule, shows the exact email or ticket it would send, and holds it if the data is stale.

Two kinds of automations.

The interesting part is knowing when not to send.

Proactive updates

No condition. It sends every run, unless a required source is stale, in which case it holds and says so.

6sends in 7 runs

A silent week would be a bug.

Exception alerts

It sends only when something qualifies. A quiet week sends nothing.

2sends in 42 checks

A silent week is the correct output.

The Composer - view both types in action.

Proactive updates

Exception alerts

Matched No match Would fire Duration

What are the benefits of having this in house?

Every value resolves from a governed table. Composer cannot invent a number.
A held send is a real state in the runner. It says which source is stale and waits.
No per-seat cost, so everyone gets a seat.