Automations

Open in product: preshos.com/automations/workflows

Automations is the scheduled side of agent work: connector syncs and recurring runs that fire without a live session behind them. The Automations module lives at /automations/workflows, opening on the Workflows tab. Sessions do interactive work; automations carry the repeating work, under the same isolation and audit guarantees.

The left rail splits the module three ways: Build (Workflows), Connect (Connectors, Schedules), Observe (Activity, Runtime, Triggers, Logs). Search, sort, column, and filter controls sit above the table; New Automation creates.
Each row carries name, description, trigger, node count, run count, last run, and status. Trigger kinds include Webhook, Database, Message, and Unknown.
Never-fired rows read Never with zero runs. Inactive is a status, not a verdict: check trigger and last run before deciding a row is dead.

Automations: Workflows table with trigger, nodes, runs, last run, and status per row

Connector packages are the unit of automation: auth, install, config, and scheduling per package, managed at /automations/connectors/[packageKey].
New scheduling goes through Inngest via function-catalog. connector-sync-runner stays dead; do not revive it for new syncs.
Connector code existing is not the same as that connector being live and connected for a tenant. The environment tool list is the source of truth for what sessions and automations can reach.

Treat /automations/workflows as the source of truth for automation surfaces. Package mechanics: SDK overview. Import mechanics worked end to end: E2E: HubSpot inbound import.