Skip to content
English
Do you need help? Customer portal
neowit.io
  • There are no suggestions because the search field is empty.

Glossary

One-page reference for the workflow vocabulary that turns up across the rest of this knowledge base. For support staff, new admins, and anyone bouncing between articles.

  • Action — A node that does something — sends a message, controls a device, halts the workflow on purpose. See Actions.
  • Active version — The committed snapshot real triggers run against. Switch the active version with Make active in Version history. See Publishing and versions.
  • Bad credentials — Integration status badge meaning the auth token was rejected on the last health check. See Integration disconnected.
  • Commit message — Short note attached to a saved version of a workflow. Required when the DAG changed. See Publishing and versions.
  • Condition — A yes/no branch node with two outputs (true and false). See Conditions.
  • Connected — Integration status badge meaning the last health check passed. See Integration disconnected.
  • DAG — Directed acyclic graph. The canvas of nodes and edges that makes up a workflow — edges always flow forward, no loops.
  • Data reference ($dataRef) — A field mode that pulls one upstream value into a node config. See References and templates.
  • Document — The accumulating bag of upstream outputs an executing task can read from, keyed by the producing node's id. See References and templates.
  • Enabled — The toggle in the Save Workflow dialog that gates whether real triggers reach a workflow. See Publishing and versions.
  • Execution — One run of a workflow from trigger to last action. Older UI copy calls this a job. See Testing your workflow.
  • Fixed value — A field mode where the literal value you type is used as-is. The default. See References and templates.
  • Health check — Periodic (every 30 minutes) probe that an integration is still authenticated and reachable. See Integration disconnected.
  • Integration — A connected external service the workflow engine can call: Slack, Philips Hue, etc. See Slack and Philips Hue.
  • Job — Synonym for execution. Older term, still used in some UI copy.
  • Mode button — The small picker on every config field that switches between Fixed value, Data reference, and Template. See References and templates.
  • mrkdwn — Slack's flavour of markdown (single-asterisk bold, <url|text> links, <@U…> mentions). See Template cookbook.
  • Node — A single box on the canvas. Always one of trigger, condition, or action.
  • Service account — A non-human identity that scheduled triggers run as. See Service account setup.
  • Stale job timeout — Org-policy setting (default 2 days) that auto-errors executions still running past the threshold. See Org policy.
  • Task — One node's run within an execution. The Logs panel's TASKS pane lists all tasks for the selected run. See Testing your workflow.
  • Template ($tpl) — A field mode that runs a Go/Sprig template expression at execution time. See References and templates and the Template cookbook.
  • Trigger — The starting node of a workflow — an event or a schedule. Every workflow has exactly one. See Triggers.
  • Trigger payload — The data the trigger event carries (e.g. the booking event's id, subject, organizer, space). Available throughout the workflow via data references. See Triggers.
  • Unable to connect — Integration status badge meaning the provider's API was unreachable on the last health check. Usually transient. See Integration disconnected.
  • Version — An immutable snapshot of a workflow's DAG and commit message. Each save that changes the DAG creates one. See Publishing and versions.
  • Workflow — The whole automation: a connected DAG of nodes (trigger → conditions → actions). See What are workflows?.

Related