Workflows wake on the field you pick, and know the customer's name

Workflows can watch one field

A workflow built on Card updated now takes a Field. Set it to Due date, and renaming a card no longer wakes it. Change the date and it runs.

Leave the picker on All fields and nothing changes. Every workflow you built before today keeps behaving the way it always has.

Card edits report themselves consistently now, whether you changed the title, the due date, the assignees, or a custom property you invented yourself. Dragging a card into another column and picking a new Status from the card are finally the same event, so a workflow watching Status catches both.

Emails that know who they are about

A link property carries the record behind it now, not only its id. Put {{trigger.card.prop.customer.name}} in an automation email and out comes the customer's name. .email does what you would expect. .title renders a linked page, board, card, or Studio project, and a Multi Reference hands you its entries and a count.

Permissions still apply. The lookup happens as whoever the workflow runs as, so if that person cannot open the customer, the variable stays a plain id.

A form can be finished in two sittings

A form answered in two steps lands as one submission. Someone fills in what they can, comes back for the rest, and the second half fills the blanks in the row that already exists. No more one person arriving as two half-answered records.

Your automations follow suit. They run once, on the first submission, so a connected calendar books a single slot and a connected Google Sheet updates the row it already wrote instead of adding a near-copy below it. The second step can only fill blanks. An answer someone already gave cannot be rewritten this way.

AI assistants stay connected

Assistants built on the current Model Context Protocol used to drop out before they finished connecting to your organization. They get all the way in now, and stay there, so an agent you point at SharpOS can work through your boards, pages, and customers.

Website uptime keeps its last reading

When the monitor behind Website analytics cannot be reached, the panel shows the last reading it has and marks it out of date. Before, you got an error, which looked a lot like the site itself being down.

Also in this release

The hub is quicker on every screen you open while signed in. An assistant or an integration can set a property across a whole board of cards in one go instead of one card at a time. The chat widget no longer loads as an empty box on a site that is not in its allowed domains, and public forms are better protected against junk submissions.