Imaginess
Start free trial
Automations

The follow-up nobody has time for

Written as a sentence: when a status changes to Won, move the row and email the family. Set it once and stop remembering it.

Included on Growth and up

Start free trialBook a demo

Say it in a sentence

The builder reads the way you would describe the rule to a colleague, because three unlabelled dropdowns is how rules get configured wrong.

  • Trigger on a status change, a new row, or a form submission
  • Move a row, set a field, create a row, notify someone
  • Send an email template, personalised per row
  • Turn any rule off without deleting it

Scheduled in your club's time

Daily, weekdays, weekly or monthly - and dated triggers that fire a set number of days before or after a date on the row.

  • No separate timezone setting to get out of step
  • Daylight saving handled by skipping, not by guessing
  • A rule switched back on recomputes rather than firing for every missed day

A history that tells the truth

Every run is recorded - succeeded, failed, or skipped with the reason.

  • See exactly which rows a rule touched and when
  • Failures name the action that failed
  • Skips explain themselves in words you can act on
  • One failing action never stops the rest of the rule

Bounded on purpose

An automation is a side effect of somebody's edit, and it is never allowed to break that edit.

  • A broken rule cannot fail the change that triggered it
  • No arbitrary code, no template language, no open webhooks
  • Automated email still goes through the consent gate
  • Admin-only to create; the whole club feels the effects

Questions

Every automation keeps a run history, including the runs that deliberately did nothing and why. "It isn't firing" is the only real question about an automation, and a rule with no visible history cannot answer it.