AutoVerse Workflow Controller icon

AutoVerse Workflow Controller

Enterprise workflow orchestration, execution control, and monitoring for n8n

Actions44

Workflow → Bulk Activate

AI-generated

Summary

Activates one or more n8n workflows in sequence through the n8n public API. It can optionally purge pending executions and clean up Telegram pending updates first, and it returns a per-workflow result list.

Inputs

  • workflowSelectionMode — How to choose workflows: searchable list (single), multiple from list, current workflow, or by URL/ID. Default is list.
  • workflowId (required) — Single workflow, shown when the mode is list.
  • workflowIds (required) — Multiple workflows, shown when the mode is multiple.
  • workflowIdManual — Workflow URL, ID, or comma-separated list of them, shown when the mode is manual. URLs are parsed to extract the ID, and duplicates are removed. At least one workflow must resolve or the node errors.
  • dropMissedEvents — Default true. Before activating, purges executions in new, running and waiting status for each workflow. Running executions are stopped and the others are deleted. It also records a dropBefore timestamp in workflow static data, which Message Freshness Guard can use to detect stale events.
  • triggerProvider — Shown when Drop Events is on. Options are None, Generic Webhook, Telegram and WhatsApp Cloud. Only Telegram performs a real cleanup. Generic Webhook and WhatsApp Cloud only return a warning that external queues can't be cleared from n8n.
  • telegramBotToken (required) — Required when the provider is Telegram. Used to call Telegram's deleteWebhook with drop_pending_updates before activation.
  • continueOnError — Default true. If a workflow fails, the failure is recorded and the loop continues. If false, the first error is thrown and stops the run.

Output shape

One output item per input item, with json.results holding an array with one entry per workflow.

Successful entries contain workflowId, workflowName, action ('activate'), success, message, dropMissedEvents, dropBefore, lastActivatedAt, purgedExecutions (per-execution action and success), and providerCleanup. Failed entries contain workflowId, action, success:false and error. Purge and cleanup problems are reported inside the entry and don't fail the activation. The Telegram bot token is not echoed in the output. Execution deletion may not be supported on some n8n versions, and this appears as an error in purgedExecutions. Requires n8nApi credentials.

Examples

Example 1: Re-enable several workflows after maintenance without processing the backlog.

Workflow Selection: Multiple From List; pick workflows; Drop Events Received While Inactive: true; Trigger Provider: None; Continue On Error: true.

Example 2: Reactivate a Telegram-triggered bot and discard pending Telegram updates.

Selection: By URL or ID; Drop Events: true; Trigger Provider: Telegram; Telegram Bot Token set.

Example 3: Activate a comma-separated list of workflow IDs, stopping at the first failure.

Selection: By URL or ID with 'id1,id2,id3'; Drop Events: false; Continue On Error: false.

Links

Discussion