The repeated part runs whether or not anyone remembers.
One trigger, one condition, one action, chosen from what the workspace actually supports. No scripting language, and nothing to debug at three in the morning.
When
a task moves to In review
If
priority equals high
no match
Then
assign Ada
Execution history
Waiting for the first run.
Work that comes back
Some work repeats. It should not need reminding.
Recurring tasks
The next occurrence is created on schedule, and the series is edited in one place.
Reminders
A task nudges its owner at a date and time they chose.
Dependencies
Work stays marked blocked until its prerequisites close, then says what it unblocked.
Templates
Work that starts the same way each time starts from the same shape.
Webhooks
Events, not polling.
Veyrd records versioned domain events and projects them outward. An endpoint subscribes to the types it can process, and nothing else.
- A catalogue grouped by resource, searchable by name
- Schema versions and payload fields shown per event
- Delivery history, a test send and a rotatable signing secret
- Deprecated types name their replacement
Early access
Open a workspace. Write the first line.
We’re opening Veyrd to teams in waves. Join the waitlist and we’ll email you when your workspace is ready.