Action nodes
Action nodes create, update, or send things. They run in the order you connect them and each one can pass data to nodes further down the chain.Create task
Creates a new task in your workspace when the workflow reaches this node.
After this node runs, the created task’s data is available to downstream nodes via
{{lastTask.id}}, {{lastTask.title}}, and other {{lastTask.*}} variables.
Example configuration:
- Title:
Set up environment for {{project.name}} - Priority:
high - Due date offset:
3
Update task
Modifies an existing task’s status or priority. By default it targets the most recently created task in the current run ({{lastTask.id}}), but you can point it at any task ID.
Status options:
backlog, todo, in_progress, in_review, done
Priority options: low, medium, high, urgent
Example use case: After an Approval Gate passes, mark a deployment task as done and move on.
Create note
Creates a new note in your workspace.
After this node runs, the note’s data is available via
{{lastNote.id}}, {{lastNote.title}}, and other {{lastNote.*}} variables.
Example configuration:
- Title:
{{project.name}} — Kickoff - Content:
Goals, milestones, and team assignments for {{project.name}}.
Update note
Updates the content of an existing note. Useful for appending information to a running log note or updating a document after upstream steps complete.Create calendar event
Creates a new calendar event in your workspace. Use this to schedule follow-up meetings, deadlines, or review sessions automatically as part of a workflow.Duplicate entity
Creates a copy of an existing project, task, or note. Useful for templating — keep a master template item and duplicate it each time a workflow fires.For each
Iterates over a list and runs the connected downstream nodes once for each item in the list. Use this to process a collection of items returned by a previous step, such as a list of tasks from an API response.Send email
Sends a transactional email to a specified address. This node uses Navis Ops’s built-in email sending infrastructure.Send Slack message
Posts a message to a Slack channel via a Slack incoming webhook URL.
Example message:
Task completed: {{trigger.entity_data.title}}
Send Discord message
Posts a message to a Discord channel via a Discord webhook URL.HTTP request
Makes an outbound HTTP request to any external API or webhook endpoint. This is the most flexible action node — use it to call Slack, GitHub, Stripe, your own backend, or any service that accepts HTTP.
Requests time out after 10 seconds. After this node runs, the response is available via
{{lastHttpResponse.data}}, {{lastHttpResponse.status}}, and other {{lastHttpResponse.*}} variables.
- Post to Slack
- Trigger a CI/CD pipeline
- Read from an API (GET)
Logic nodes
Logic nodes don’t create or send anything — they control how execution flows through your workflow.Condition
Evaluates a true/false expression and branches the workflow into two paths. The Condition node has two output handles: True (top) and False (bottom). Edges leaving a Condition node are automatically labeled so you can see which path is which on the canvas.
Available operators:
Example — route blocked tasks differently:
- Field:
trigger.entity_data.status - Operator:
equals - Value:
blocked - True path: Create an escalation note and urgent follow-up task
- False path: Log the status change with a low-priority task
Delay
Pauses the workflow for a specified amount of time before the next node runs.
The maximum delay per node is 30 seconds. For longer waits, chain multiple Delay nodes in sequence, or redesign using a Scheduled trigger.
Long-running delays use a checkpoint-and-resume mechanism so they don’t block other workflows from running. The workflow pauses cleanly and picks up where it left off when the delay expires.
Approval gate
Pauses the workflow entirely and waits for a human to review and approve before execution continues. No subsequent nodes run until someone clicks Approve & Resume in the Runs panel.
How the approval gate works:
1
Workflow pauses
When execution reaches the Approval Gate node, the workflow stops immediately. The run’s status changes to Paused in the Runs panel.
2
Reviewer is notified
The Runs panel shows an amber pause icon next to the paused run, with the gate’s label and instructions visible when expanded.
3
Reviewer approves
The reviewer opens the Runs panel, expands the paused run, reads the instructions, and clicks Approve & Resume.
4
Workflow continues
Execution resumes from the Approval Gate and runs all remaining downstream nodes.
- Gate label:
Lead Approval - Instructions:
Review CI results and staging environment before approving production deploy.
Connecting nodes
Hover over any node on the canvas to reveal small circular handles on the top (input) and bottom (output) edges. To create a connection:- Click and drag from an output handle on one node.
- Drag to an input handle on another node.
- Release — an animated arrow line appears showing the direction of execution.
Configuration panel
Select any node to open its configuration panel on the right side of the canvas. This is where you set all the node’s fields, choose dropdown values, and insert variables using the{{ picker. Changes save automatically as part of the workflow’s auto-save.
Next steps
Variables
Use dynamic data from triggers and previous nodes in your node fields.
Templates
See pre-built workflows that combine these nodes into complete automations.