Automations
Draw the rule, don’t write it
Every rule is a small diagram: something starts it, a condition narrows it, and one or more things happen. You can read someone else’s rule at a glance, which is the part that matters six months later.
Everything is a node
Drag a trigger, a condition, an action. Connect them. The shape of the rule is the rule — there is no second place where the real logic hides.
- TriggerStatus became “On site”
- LogicIf label is C or D
- FieldShow “Installations”
- ActionNotify the owner
- ActionGenerate the PDF
Something has to start it
A record appears or changes hands. A field takes a new value. A date arrives. Somebody presses a button you put on the form yourself.
A few of them, from the trigger menu.
Then something happens
The engine works on the record — moving its status, assigning it, mailing someone, posting to your own endpoint, filing it away.
Run server-side, whether or not anyone has the form open.
Or the form itself reacts
A different mechanism, worth keeping separate: these run while somebody is filling the form in. One answer filters the options of the next, or brings a whole section into view. You draw them on the same canvas, but they happen in the browser rather than on the server.
Know what it did
Every run is recorded — what set it off, which actions succeeded, which failed, how long it took. You can replay one, and you can try a rule against a real record before it goes live without touching that record.
Build your first form today
Start on the free plan and grow the plan as the team grows. No setup fee, no mandatory consultant.
No credit card required