Eternet Portal Documentation

Automation Rules

Current portal role

The Automations page loads the automation resource through the Eternet API and presents it in the Automation Manager. It is the portal surface for browsing and managing the automation records exposed by that service.

Execution boundary

Rule execution, trigger evaluation, and resulting actions belong to the backend automation/device services and their configured integrations. A listed rule is not proof that its trigger is currently firing; execution status depends on the service’s own runtime and telemetry.

Operational checks

  • Confirm the automation record is returned by the API.
  • Check its configured trigger, target, and action in the backend contract.
  • Verify runtime logs or resulting telemetry before claiming an automation executed.

How to explain an automation

An automation is best presented as a rule connecting an observed condition to an intended action. The portal page is the operator-facing place to review the automation records exposed by the Eternet Automation API. The underlying record may refer to a trigger, stream, resource, condition, target, or action. These pieces together define what the backend is expected to evaluate. The page’s purpose is not to replace that evaluation engine; it makes the configuration discoverable and manageable in the context of the rest of the IoT platform.

Customers often interpret a visible rule as proof that a device action has occurred. Avoid that implication. A saved configuration can be syntactically valid yet fail to run because the source stream is silent, a condition cannot be evaluated, the target is unavailable, or an integration lacks permission. Likewise, a rule can execute while the portal’s latest list is stale. The reliable evidence of execution is a service execution record, backend log, downstream command acknowledgement, or resulting telemetry—not merely a row in the UI.

Review and validation workflow

When reviewing an automation, first identify the resource and source signal, then inspect the comparison or condition and its expected value type. Verify that a numeric rule receives a numeric value and that text or boolean conditions use the format understood by the service. Next confirm the target entity and action are valid, that the target is reachable, and that the service identity is authorized to perform the action. Finally, exercise the rule with a controlled test condition and examine both the backend execution evidence and the target’s observed response. This method separates configuration errors from transport failures and from UI refresh delays.

Automation behavior can also depend on timing, debounce, schedule, retry, and duplicate-message policies. Those policies belong to the backend implementation and should only be described when verified in the actual record and service code. The portal may present only a subset of runtime diagnostics. If status or history is not exposed in the response, say that the portal can show the configured rule but that execution observability must be checked in the responsible service.

Customer outcomes and boundaries

Used with devices, hubs, and vehicles, automation rules can reduce repetitive monitoring and make platform behavior more consistent. They help teams express operational intent in reusable configurations instead of relying only on manual intervention. Demonstrations should use a non-disruptive condition and a safe target, particularly when actions could affect equipment or customer data. The customer should understand which component evaluates the rule, which component performs the action, and where success or failure is recorded. The portal supplies a unified management surface; trigger processing and side effects remain the responsibility of the Automation Service and the integrations it invokes.