Trigger
Configure the exact event that starts the rule.
Feature
Automate the repeatable step and keep the result visible.
Use project events and transition actions to run defined responses while preserving the surrounding work history.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Choose the trigger
Configure the project event that starts the automation.
- 02
Define the action
Set conditions and the action to execute.
- 03
Inspect the run
Review the concrete trigger, actor, actions, timing, and result.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Conditions and actions
Make rule conditions and resulting actions explicit.
Workflow action
Run a configured automation from a workflow transition.
Run detail
Keep each execution and its result inspectable.
Control point
AI follows the same boundary.
Where AI is enabled, accessible context and review-oriented flows apply to the surrounding workspace rather than bypassing its controls.
- Scoped context
- Configured provider
- Visible proposals
- Human decision
Deployment and security
Control the deployment and the boundary.
Use TOW Cloud, run TOW on controlled infrastructure, or operate an air-gapped Docker Compose deployment. Permissions, identity settings, exports, and AI provider choices stay visible to administrators.
Explore self-hosting
FAQ
Questions worth answering clearly.
Current product, deployment, and commercial boundaries.
Is trigger implemented in TOW?
Yes. Trigger, Conditions and actions, Workflow action, Run detail are part of the current product surface and are backed by the linked implementation evidence.
Can this be self-hosted?
Yes. The capability is available within the TOW application in a configured self-hosted deployment.
See TOW in your environment