Follow-ups that run themselves
Pick a trigger, add conditions, chain the actions. Handoffs, reminders and status posts happen the moment a row changes.
Run history live
Pricing page review → assigned to Tomás
Posted in #autumn-launch
Due-date nudge sent to Lena
Weekly digest sent to 4 people
Form answer → row 7, owner Priya
Triggers on any change
A status moves, a date passes, a form arrives, a pull request merges. Start from any of them.
Assign the next person
Route work by column value, by workload or round-robin across a group.
Reminders people read
Nudges go to the owner two days before a due date, in chat or email, with a link to the row.
Run history you can check
Every run is logged with what changed. Re-run a failed step with one click.
Set up in three steps
- 1
Choose a trigger
Start from a recipe or build from scratch: when a row is created, changed or due.
- 2
Add conditions
Only if priority is high, or the owner is on a given team. Combine as many as you need.
- 3
Chain the actions
Assign, set dates, post a message, create rows in another project or call a webhook.
Move your next project into a table.
Import a spreadsheet or start from a team template. Most teams have their first view running in ten minutes.