Dailify
Log inJoin

Human

Human steps send work to people via the inbox: approvals that pause a run, or notifications that inform without blocking.

Overview

Use Approval when someone must explicitly allow the run to continue. Use Notification when you only need to surface information in the inbox while the graph keeps moving. Both land in the app inbox; see Inbox for the product-level tour.

Steps in this family

  • Approval: pause until approve or decline; map reviewer outputs for downstream branches.
  • Notification: raise an inbox notification without pausing the run for a gate.

Configuration

For approvals, use General for labels and reviewer-facing messaging, and Output to map decision metadata (for example decision enum, timestamps) from {{exe.*}} after a response. There is no Execution tab: the work happens in the inbox UI instead of inside a model or sandbox. Notifications follow the same sheet pattern with copy and payload fields appropriate to that template.

Data flow

While an approval is waiting, the run sits in a paused state; after action, the runner emits the mapped output object like any other step so branches and AI steps can continue. Notifications emit without blocking in the same way as other non-gate steps unless the product adds explicit waits.

Related