What is the Cutover Nodemap?
The Nodemap in Cutover is the underlying structure that controls how runbooks execute. It represents each task as a node and maps the relationships between tasks (for example, which tasks must finish before another can begin).
Nodes = tasks
Relationships = dependencies that determine sequencing
This framework decides when tasks are ready to start, how they connect to each other, and how the overall runbook progresses.
Why it matters:
Ensures execution order is respected.
Determines when tasks are eligible to start (“On Task Startable” events tie directly to the Nodemap logic).
Enables large, complex runbooks to be managed dynamically with confidence.
For developers / integrations:
When you query runbooks or listen for events, Cutover is using the Nodemap behind the scenes to decide which tasks are actionable and when.
Where to find the Nodemap
The Nodemap can be accessed from a runbook on the top right grey bar.
Accessing the Nodemap
When you first access the Nodemap, you will see a view which details all the streams in the runbook and the sequence of tasks. Use your mouse or trackpad to zoom in and out for more detail or a broader view. You can also use the mini map on the left-hand side to jump to a specific area, or simply click and drag to move the Nodemap in any direction.
In the bottom-left corner, you’ll find quick-access options:
Download an image of the Nodemap for sharing or offline reference. Note: Only the task ids will be visible, not the full title.
Add a new task by clicking the + icon.
You can undo certain actions in the Editable Nodemap, including adding tasks, changing dependencies, and duplicating or copying/pasting tasks (undoing a newly created task will appear as a delete in the audit log).
Undo is limited to your most recent action only.
The following actions cannot be undone: deleting tasks, edits made via the edit panel, comments, and starting, finishing, or skipping tasks.
Action Bar
When you click on a task in the Nodemap, an action bar will appear at the bottom of the window.
The options displayed in the action bar depend on the task you selected, showing only the actions available for that task. Hover over each icon to understand what it can do. For more details on these icons, see our Nodemap Navigation and Selection article.
Roles
Runbook Admins
Runbook admins have full editing rights on a runbook whenever it is in an editable state: planning, a paused run, or a dynamic run. In this state, they can edit nodes as long as the tasks have not been started.
Certain edit actions in the task edit panel are still permitted for in-progress tasks, but Nodemap edits are restricted once a task has started.
All standard operations are available, but tasks can only be moved or copied to links where the target task has not yet started.
Links can also be edited provided the target node has not started.
Stream Editors
Stream editors’ permissions are mostly unchanged, with some enhancements:
Task creation: Can create tasks in their stream or any substreams, with no restriction on dependencies (e.g. inserting from the actions toolbar of another task).
Task movement: Previously blocked in the UI, stream editors can now move their tasks between any two other tasks—similar to inserting a task elsewhere.
Edit/Delete/Copy/Paste/Duplicate: No change. Stream editors can perform these actions on tasks within their stream or substreams.
Link management: Stream editors can now update, remove, or insert links if they own either the source or the target task (previously this was limited to predecessors only).
Runbook Members
Runbook members have view-only access in the Nodemap:
Can view and filter tasks.
Can click nodes to open the task edit panel.
Can download an image of the Nodemap.
Cannot make edits.