Automation

Rules that run without anyone watching.

Say when, say if, say what. The builder turns it into a workflow that runs on your sheets, with a log of every run.

Book a demo

Automation: Flag blocked work

Draft

Trigger

Row createdRow updatedCell changedDate reachedForm submitted

WhenCell changedStatus
IfStatus is BlockedCondition
ThenApply formattingTurn the row red
ThenSend notificationEveryone with access

Thirteen actions

Set cellApply formattingCreate rowDelete rowLockUnlockAssign peopleSend notificationAlert by emailTeamsSlackWhatsAppCall webhook

Run log

UAT sign-off: ProcurementSet to Blocked · 2 actions ranJust now
Integration test cycle 2Skipped · Conditions not met09:12
UAT: FinanceSkipped · Conditions not met09:31

Runs on Dana Whitfield’s access, and switches off if she loses it.

Anatomy of a rule

When, if, then.

1
When
A row is created or updated, a cell changes, a date arrives, or a form is submitted.
2
If
Optional conditions on any column, joined with AND or OR.
3
Then
One or more actions, run in order.
4
Log
Every run is recorded, with the trigger count and last run time.

Actions

Every action a rule can take.

Set a cell

Write a value into a column.

Apply formatting

Colour the row or cell.

Create a row

Add a task, a risk or a follow-up.

Delete a row

Remove rows that meet a condition.

Lock and unlock

Freeze a row once it is signed off.

Assign people

Set the owners from the trigger.

Send a notification

Ping the person, specific people, or everyone with access.

Alert by email

Subject and body with values from the row.

Post to Teams

Send to a Microsoft Teams channel.

Post to Slack

Send to a Slack channel.

Message on WhatsApp

Alert on WhatsApp.

Call a webhook

Hand off to any system that takes a request.

Safe by design

Rules run on their owner's access.

An automation runs with the access of the person who saved it. If they lose access to the sheet, or to a sheet the rule copies rows to, the rule switches itself off and says why.

An off switch
Turn a rule off without deleting it, and back on when you are ready.
Failures are visible
A failed step is recorded in the log, not swallowed.
Destinations are checked
Webhook and channel targets are validated before a rule is saved.

ERP Transformation

Grid view · 25 rows

TaskStatus

Phase 2 · Build and migrate
Migrate vendor master data
In Progress
Aisha6 Oct
Build procurement-to-finance integrations
Complete
Tomas18 Sep
Integration test cycle 2
In Progress
Grace2 Oct
Cutover runbook review
In Progress
Tomas23 Sep
UAT: Finance
In Progress
Grace6 Oct
UAT sign-off: Procurement
In Progress
Not StartedIn ProgressBlockedComplete
Dana14 Oct
Phase 2 Go-Live
Not Started
Dana19 Oct

Row coloursBlockedOverdueComplete

Automation: Flag blocked work

WhenStatus changes
IfStatus is Blocked
ThenNotify everyone with access

UAT sign-off: Procurement is blocked. Sent to everyone with access to ERP Transformation.

PMO Overview · Blocked work

UAT sign-off: ProcurementERP
Vendor firmware certificationGrid

FAQ

Questions people ask.

A row being created, a row being updated, a specific cell changing, a date being reached (on the day or a set number of days before or after), or a form being submitted.

Set a cell value, apply formatting, create or delete a row, lock or unlock a row, assign people, send an in-app notification, send an email, post to a Microsoft Teams or Slack channel, message on WhatsApp, or call a webhook.

The person who last saved it. If that person can no longer edit the sheet, or a destination sheet, the rule is switched off and its log records why, so an automation cannot quietly widen access.

Yes. Each automation keeps a run log with its trigger count and last run, and failures are recorded rather than hidden.

Bring one plan. See it run.

In 30 minutes we set up a workspace like yours and show sheets, Gantt, dashboards, capacity and a PM agent at work.

Book a demo Explore the platform