AutoVerse Workflow Controller icon

AutoVerse Workflow Controller

Enterprise workflow orchestration, execution control, and monitoring for n8n

Actions44

Workflow → Activate Workflow

AI-generated

Summary

Activates one or more n8n workflows through the n8n public API (POST /workflows/{id}/activate). Optionally purges pending executions and clears Telegram pending updates first, so events received while the workflow was inactive aren't processed after reactivation.

Inputs

  • Workflow Selection — How to pick targets: searchable list (default), multiple from list, current workflow (must be saved), or by URL/ID.
  • Workflow Name or ID (required) — Single workflow, shown when selection mode is 'list'.
  • Workflow Names or IDs (required) — Multiple workflows, shown when selection mode is 'multiple'.
  • Workflow URL or IDs — Shown in 'manual' mode. Accepts workflow URLs, IDs, or comma-separated IDs; URLs are parsed to extract the ID and duplicates are removed.
  • Drop Events Received While Inactive — Default true. Before activating, deletes executions with status new/waiting and stops running ones for the workflow, runs provider cleanup, and records a 'dropBefore' timestamp in workflow static data (usable by the Message Freshness Guard operation).
  • Trigger Provider — Shown when dropping events. None, Generic Webhook, Telegram, or WhatsApp Cloud. Only Telegram is actually cleaned up; Generic Webhook and WhatsApp Cloud return a warning that external retry queues can't be cleared.
  • Telegram Bot Token (required) — Required when provider is Telegram. Used to call Telegram's deleteWebhook with drop_pending_updates=true before activation.

Output shape

A single item with a results array containing one entry per workflow: workflowId, workflowName, action, success, message, dropMissedEvents, dropBefore, lastActivatedAt, purgedExecutions (per-execution outcomes), and providerCleanup.

Failures are recorded as {workflowId, action, success:false, error}, but this operation always rethrows the error (continue-on-error is fixed to false), so the first failure stops the run unless the node's own Continue On Fail setting is on. Purge and cleanup problems are reported in the output rather than thrown. Execution listing during purge is limited to 10 pages per status. Delete of executions may not be supported on older n8n API versions. Requires an n8nApi credential.

Examples

Example 1: Reactivate a Telegram bot workflow after maintenance without replaying backlog messages

Workflow Selection: From Searchable List; pick the workflow; Drop Events Received While Inactive: true; Trigger Provider: Telegram; Telegram Bot Token: your bot token.

Example 2: Simply turn on the workflow that contains this node

Workflow Selection: Current Workflow; Drop Events Received While Inactive: false.

Links

Discussion