Horizon offers packages, plugins, and workflows to manage complex actions associated with your space or site. The workflow builder is meant to synthesize the process of data collection, data management and processing, and site modification through the creation of AI-enabled workflows.

Workflows consist of execution 'nodes' and relationships. A GUI allows users to build repeatable workflows. There are several types of 'nodes' that can be used to create workflows:

- trigger nodes. Trigger nodes kick off the execution of workflow by various means such as a cron job, an API call, a manual 'start' pressed by an authorized user, and more.

- resource nodes. Resource nodes are assets which are stored in Horizon which serve as starting points. For example, a 'source collection' is a potential resource, as is a space table with data in itself.

- transform nodes. Transform nodes take resources and transform them in various ways. Transformations include sorting and ordering resources (by 'most recent', or 'alphabetical'), or AI transformations (using resources as inputs.

- hold nodes. Hold nodes pause execution. Hold nodes must be linked to trigger nodes, which trigger continued executions.

- dispatch nodes. Dispatch nodes are the final output of a workflow. For instance, an AI-transformed summary of events might be 'output' as social media posts, or sent to be saved as a value in the Horizon application.

Every workflow, consists of various execution nodes. Each step of the workflow is called an execution. Each execution takes outputs of previous steps as inputs and returns artifacts as export to pass to 'downstream' nodes.

A job is a single workflow procedure. Workflow jobs can run, be scheduled, be complete, and more. All artifacts at every step of a workflow execution are saved and available via an API. Workflow artifacts can be retrieved.