Docs

Reading the trajectory

The walk, the overview, choosing funnels, backwards moves, and cross-track handoffs.

A funnel is a field whose values come in an order. The trajectory draws it as a track and shows what the automations do to a record at each stage.

The walk

The walk puts one stage in focus and unfolds what happens there: puts a record here is the automations that write this value; waiting here is the ones whose enrollment criteria name it; then writes is every other field those automations set off, with the ones another system reads marked gold. The rest of the track collapses to a spine you step along with ↑ and ↓; space plays through the rungs; o switches to the overview.

The footer reads the focused rung as a sentence with the counts behind it.

The overview

Every rung at once, for comparing stages against each other: which stage has the most arrivals, which has nothing automated at all. The four toggles hide waiting automations, side-channels, movement and unautomated stages.

Backwards moves

An automation that waits at one stage and writes an earlier one moves records backwards. It is drawn in red, and the footer counts them. Some are deliberate, like recycling stale leads; the view exists so that none are accidental.

Cross-track handoffs

When a portal has more than one funnel, a contact lifecycle and a deal pipeline, an automation that waits on one and writes the other is a handoff between tracks. The line is routed under the block to the other track, so the two funnels read as one machine.

Choosing funnels

Which fields are funnels is a judgement about the business, not something the platform knows. Choose funnels… ranks every field by how many automations name specific values of it and whether an ordering has been collected; tick the ones that carry the real pipeline. The same choice is made in Settings → Ontology, where it is written to the workspace so the command line agrees.

A field with no collected ordering says so instead of drawing an empty track: run the stages collector, or check that the field is an enumeration.

Light the structure

light the structure opens the structure view beside this one and lights each step's automations and fields in it as you walk. The two views then move together.