Workflows that run as often as your work does.

Yes. Wisegrid ships a visual automation builder on every sheet. Each rule is a trigger, an optional set of conditions, and an ordered stack of actions that you assemble by clicking, with no scripting. Rules run automatically as the work happens, and editors and owners can create or edit them.

Three kinds of trigger. "When a row changes" fires on a save (a value becomes something, changes, or becomes empty). "When a new row is added" fires once on insert, including rows that arrive through a form. "On a date" fires on the clock, scheduled relative to a date column with an offset in days and an hour of the day. Form submissions run the same rules an editor would trigger.

Notify someone (a fixed email address or a contact column on the row, with {{Column Name}} placeholders in the subject and body), set a cell, set a date (today or a fixed date), assign a person, clear a cell, move a row to another sheet, or copy a row to another sheet. You can also request approval or request an update. A single rule runs up to ten actions, top to bottom.

Yes. The move-row action relocates the triggering row to another sheet, and copy-row duplicates it into another sheet, so "when Status becomes Done, move the row to Archive" is a few clicks. The target sheet is access-checked both when you save the rule and again when it runs, and automation writes never re-trigger automations, so a move or copy cannot start a loop.

Yes. Drop a request-approval step into a rule and the run suspends at that point. The approver gets an email linking to a decision page that shows the rule, the sheet, and a short whitelisted summary of the row. On approval the run resumes at the exact next action; on rejection it can run an optional reject branch. A rule can hold one approval gate in this version.

No. Approvals are email-keyed and token-authorized. The approver clicks the link in their email and decides on a server-rendered page without logging in, and the decision never provisions a seat or touches your member list. If the email happens to match an existing account, that match is recorded as advisory only.

A rule can carry one group of condition clauses joined by AND or OR, up to twenty clauses. Clauses support equals, not-equals, contains, greater or less than, is-empty, is-not-empty, and is-one-of, plus transition checks (becomes, changes, becomes-empty) on row-change triggers. The valid operators are filtered by each column type, so a rule that saves is a rule that evaluates cleanly at run time. Nested groups are not in this version.

No. Wisegrid does not meter automation runs per tier, so a busy month never throttles your rules. You pay for your plan capacity (the cell ceiling), and the automations come with it. Build the workflows your process needs without rationing runs against a counter.

Yes. Every rule keeps a run history you can read per rule or across the whole sheet. Each run shows its outcome (sent, skipped, or errored) on a specific row, and date-triggered failures carry a reason, so a quiet failure never hides and you can answer "did the reminder go out?" with a receipt.

Yes. Every create, edit, enable, or disable writes an immutable version snapshot in the same transaction, recording who changed the rule and when. A version-history view shows how a rule evolved, which matters when a workflow quietly stops doing what someone expected.

The builder uses the same shape a Smartsheet user already knows: a trigger, conditions, and a stack of actions. You get cross-sheet move and copy, real suspend-and-resume approvals, full run history, and version history on every rule, with no per-tier monthly run meter to watch. It is one flat price, with more of everything.