ReachAutomation
The follow-through, on the record. Workflows that run on your triggers and keep a record of every run, plus reports over everything they touch.
Two parts of Automation. Each with a page of its own.
- WorkflowsThree triggers that matter, six actions that do real work, and a run history that records every step, including the ones that failed.
- ReportsSaved questions over your money, pipeline, engagement and people: grouped, totalled, and shown as a table, a chart, or the one number the board asks for.
If this, then actually do it. And keep the record.
A workflow runs on a real trigger, checks the condition you set, and runs its steps in order: once per crossing, never once per minute.
- A stage changes, a gift lands, or a score crosses your line
- Crossing fires once; sitting above the line doesn’t re-fire
- One condition if you want it: eight comparisons, and an unreadable one skips the run
- Six actions that write real records, visibly
- Off until you say: a draft never runs against your data
- Every run kept, step by step, errors and all
Ask a standing question. A report is saved, not re-exported.
A report is a definition: what it runs over, how it groups and totals it. It stays current every time you open it, so the month-end scramble becomes opening a page.
- Over transactions, deals, engagements or contacts
- Filter it, group it, and total it: count, sum or average
- A table, a bar, a line, or a single number
- Money never cross-sums: currency is grouped or pinned
- Saved once, current every time you open it
Automation you can trust. Because you can see exactly what it did.
Over what matters
Reports run over transactions, deals, engagements and contacts: the money, the pipeline, and the people.
Your columns, your cuts
Choose what it keeps, how it groups, and what it totals. The report is a saved question, not a one-off export.
Shaped to be read
A table when you need the rows, a bar or line when you need the shape, a single number when that number is the point.
And the raw feed
A read API with scoped tokens, and webhooks with delivery records, for the questions a report builder shouldn’t have to answer.
Stop being the automation. The beta is open now.
Something small and annoying that you do by hand today: when a first gift lands, bump the giving score, set the donor’s status, put the acknowledgement on the record, and ping your webhook. Ten minutes to build, and one thing nobody has to remember again.
The run records it (which step, when, and the error message) and writes every remaining step as skipped rather than pretending they ran. Failures are visible in the run history, not silent.
Not yet. A workflow today is a straight line of steps run in order, with no branches and no delays. Both are designed into the data model and neither has shipped, and we would rather name that than let you plan a drip sequence around it. For timed sequences, Pulse journeys have real waits and branches.
They can create records of any type you’ve modelled: a gift record on every confirmed donation, say. They don’t yet fire when an object changes; today the triggers are stage changes, transactions and engagement thresholds.
Group by month and put the sum on a line; comparison is what group-by is for. For anything the builder can’t express, the read API returns the raw rows.