Workflows.

Workflows are how the apps act like one suite without blurring which app owns which record. rsvp creates bookings. work forms create form submissions. bill creates invoices. pact creates documents. A workflow listens for one of those object events and decides what should happen next.

The basic shape

1. Source. An app creates or updates an object, like a booking, form submission, invoice, or document.
2. Event data. The workflow receives a snapshot of the object data it can use in conditions and action fields.
3. Conditions. Optional filters decide whether the event should continue. In v1, all conditions must match.
4. Actions. The workflow creates the next object or message, such as a task, contact, notification, or SMS.

Forms are common triggers

Forms are often the fastest way to start. Build a public form in work, publish it, then create a workflow with Form submitted as the trigger. You can scope the workflow to one form, or let it listen to every public form in the tenant.

Form answers become event data. That means a task title, contact name, assignee note, or message body can include values from the submission without copying and pasting.

Where to start

In work, open workflow templates to install a ready-made pattern, or use New workflow to build one directly. The builder shows the path from source object to event data to conditions to output before anything is saved.