Declare the trigger.
Match time, object creation or property changes, dataset publication, stream observations, file creation, or named events. Each condition carries the facts relevant to that occurrence.
Start the right operation when something changes.
Define standing rules that start an Action, Workflow, or operational agent when an event, data change, file arrival, or schedule matches.
What should start when something happens?
- Condition
- Event, object, dataset, stream, file, or time
- Target
- Action, Workflow, or operational agent
- Inputs
- Declared values and occurrence bindings
- History
- Trigger, dispatch, and resulting operation
One occurrence. One declared operation.
Switch between a file arrival, an object change, and a scheduled time to see what each rule starts.
FileVersionCreated
file_version → document input
Declared rule
Use the configured authority and occurrence bindings.
Document processing Workflow
Ready for a matching occurrence
The new immutable file version becomes the declared file input. Simulate the occurrence to follow its dispatch.
An Automation starts the work. A Workflow carries it forward.Explore Workflows
How Automations work.
Explore document intakeBind the starting context.
Pass declared values such as the subject key, captured dataset transaction, or immutable file version to the operation. Keep the trigger connected to the work it starts.
Choose what starts.
An Automation can target an Action, a Workflow, or an operational agent. The selected operation retains its own rules, authority, and execution history.
Separate the trigger from the process.
An Automation decides when work starts. A Workflow defines how it continues. Time rules also declare a timezone and what to do with a missed scheduled occurrence.
Follow it into the source.
An exact excerpt from the repository, with the complete source file available to inspect and download.
// ActionTarget selects one governed operation. A targeted Action declares its// subject with the same literal/occurrence source type as every other argument.func ActionTarget(name string, subject ...Argument) AutomationTarget { target := AutomationTarget{Kind: TargetAction, Name: name} if len(subject) > 1 { panic("ActionTarget accepts at most one subject") } if len(subject) == 1 { copy := cloneArgument(subject[0]) target.Subject = © } return target}func WorkflowTarget(name string) AutomationTarget { return AutomationTarget{Kind: TargetWorkflow, Name: name}}func AgentTarget(name string) AutomationTarget { return AutomationTarget{Kind: TargetAgent, Name: name}Dataset publication is a dataset-level trigger, not one occurrence per changed row. Stream rules can release every waiting occurrence or coalesce to the latest. Automation dispatch grants no extra Action authority.
Read the capability referenceConnect the next part of the process.
Bring us a process.
We'll build it with you.
A business process, the systems it touches, and the rules it needs to follow.