Signal for the
eventual output. Automate.ax resolves its inputs, validates them, executes the
action, validates its output, and then makes that output available to dependent
work.
Inputs
Action inputs are typed object properties. Each property accepts a direct value or a compatible signal:to and text are literal values. subject is a signal, so the action
waits for the incoming email before executing.
Defaults and validation belong to the action’s schema. The action reference
documents each field, limit, and provider-specific rule.
Outputs
An action’s return value is always a signal, even when its eventual output is an object, array, primitive, orvoid.
Concurrency and ordering
Actions become ready when all their signal inputs and inherited dependencies are ready. Two calls that depend only on the same trigger can execute concurrently. Passing one action’s output to another establishes ordering. Do not add a fake data dependency just to control order. When work must wait without consuming a value, usegroup(dependency, fn) to add an explicit
dependency to the actions called inside the function.
Failures
When an action fails, ordinary dependent actions do not execute. Independent branches can continue. Usefailed(actionSignal) when another action should
handle the failure as data.
Action execution may be retried by the platform. Integration actions are
designed around their provider’s behavior, but an automation should not assume
that several separate actions form one transaction.