Free Intro Class
    Botspot Logo

    Menu

    LoginSign Up

    agenthub · system.pulse

    Pulse

    Emit a progress signal to whatever is watching the run. Triggered by a flow edge, so it fires when a node completes rather than when data arrives.

    category Systemin trigger · message · progress · dataout —execution syncmodel cost none

    Why the node earns its place

    A long run is opaque from the outside. Pulse is how a graph says where it has got to — a status line, a percentage, a warning — without that reporting becoming part of the data path.

    How it works at run time

    1. 1
      Wait for the flow trigger.
    2. 2
      Emit the configured event type and message, overridden by wired inputs when present.

    What you wire

    Inputs

    • trigger *
      flow
    • message
      string
    • progress
      number
    • data
      object

    Outputs

    Nothing handed onward.

    Configuration

    KeyTypeDefault & optionsWhat it does
    event_typestringdefault "status" status · progress · info · warning · error—
    messagestring—Static message shown in UI (can be overridden by a connected message input)

    What usually goes wrong

    Watch for this

    It has no outputs; it is observed, not consumed. Wire it from a flow port, not a data port.

    Behaviour & provenance

    buildersChat & voice agents
    routesno
    side effectsnone — computes only
    replay safetynot applicable
    talks tonothing outside the run
    holdsno credentials