AutoVerse Workflow Controller icon

AutoVerse Workflow Controller

Enterprise workflow orchestration, execution control, and monitoring for n8n

Execution → Monitor Running Executions

AI-generated

Summary

Lists running and, optionally, waiting executions for one or more selected workflows via the n8n public API, returning both lists and a combined active count in one item. Read-only; it does not stop or modify anything.

Inputs

  • Workflow Selection — How to pick workflows: searchable list (default), multiple from list, current workflow, or by URL/ID (comma-separated allowed).
  • Workflow Name or ID (required) — Single workflow, shown when selection mode is 'list'.
  • Workflow Names or IDs — Multiple workflows, shown when mode is 'multiple'.
  • Workflow URL or IDs — Workflow URLs, IDs, or comma-separated IDs, shown when mode is 'manual'. URLs are parsed to extract the ID.
  • Execution Status — Status filter (Any, Error, Running, Success, Waiting). Blank/Any falls back to 'running' for the running list and 'waiting' for the waiting list. A chosen status overrides both lists, so both queries use that status.
  • Include Execution Data — Whether to include full execution data in each returned execution. Default false.
  • Include Waiting Executions — Whether to also query waiting executions. Default true.
  • Max Pages — Maximum pages fetched per query (100 per page), 1–50, default 5.

Output shape

One item per input item with json: { running: [execution objects], waiting: [execution objects], activeCount: number }.

The workflowId filter is applied only when exactly one workflow is resolved. With multiple workflows, no workflow filter is sent, so results cover all workflows on the instance. Results are capped by Max Pages. If Execution Status is set to something other than Any, both running and waiting lists use that status. waiting is empty if Include Waiting Executions is off. Requires the n8nApi credential. Errors fail the item unless Continue On Fail is enabled, which returns {error} instead.

Examples

Example 1: Check whether a specific workflow has active runs before deploying changes.

Workflow Selection: From Searchable List; pick the workflow; Include Waiting Executions: true; then use activeCount in an IF node.

Example 2: Monitor the workflow that contains this node.

Workflow Selection: Current Workflow; Include Execution Data: false; Max Pages: 1.

Example 3: Inspect running executions with their data for a workflow given by URL.

Workflow Selection: By URL or ID; paste the workflow URL; Include Execution Data: true; Include Waiting Executions: false.

Links

Discussion