Define what should happen
A rule connects an event to conditions and actions. Choose a specific trigger, describe when the rule should apply, and select the change you intend.
Use the rule preview before turning it on. Review the affected tasks and the bounded cascade if one change could trigger another rule.
Check what finished means
Completion checks can require checklist items or field values before a task is marked complete. Use a requirement people can understand and satisfy.
If completion is blocked, review the named requirement and the task details. Changing a rule should be a deliberate plan configuration action.
Pause processes and review connections
Use explicit start and pause controls to change whether a process runs. Hiding its interface leaves an active rule or repeat series active.
Webhooks send supported events to an endpoint you configure. Treat that destination as a connection to your data and review its scope and ownership before enabling it.