AutoVerse Workflow Controller

Enterprise workflow lifecycle, execution control, monitoring, and orchestration for n8n.

This package provides a polished n8n community node that feels close to a native control center: searchable workflow dropdowns, multi-select bulk actions, conditional controls, smart defaults, monitoring outputs, retry and queue protection, maintenance mode, favorites, locks, and dependency graph analysis.

Features

• Workflow lifecycle: activate, deactivate, duplicate, rename, delete, import, export, tag, favorite, and maintenance mode.
• Execution control: stop, retry, restart failed executions, monitor running executions, cancel queued executions, live polling, and bulk controls.
• Monitoring: health score, failure rate, consecutive failure detection, average duration, last successful run, last failed run, execution analytics, and smart alerts.
• Orchestration: dependency graph analysis, graceful shutdown, auto recovery, workflow locks, queue protection, rate limiting, loop protection, and live state sync.
• Hard pause controls: deactivate or activate while dropping missed events, purging stale executions, and guarding message freshness after triggers.
• UX: dynamic workflow loading, searchable selectors, multi-select workflow support, status-rich labels, toggles, conditional fields, and minimal manual ID entry.
• Enterprise shape: modular TypeScript, reusable API client, retries, timeouts, pagination, ESLint, Prettier, Vitest, Docker, and GitHub Actions.

Install

npm install n8n-nodes-autoverse-workflow-controller

For self-hosted n8n, install it as a community node from the n8n UI or in your custom extensions directory.

Credentials

Create an n8n API credential and choose one authentication mode:

• API Key: recommended for most self-hosted and n8n Cloud usage.
• Bearer Token: useful behind gateways or internal identity proxies.
• OAuth2: available for enterprise identity setups that issue compatible bearer tokens.

Use the base URL without /api/v1, for example:

https://n8n.example.com

Development

npm install
npm run typecheck
npm run lint
npm test
npm run build

During local development:

npm run dev

Package Structure

credentials/
  N8nApi.credentials.ts
nodes/
  WorkflowController/
    WorkflowController.node.ts
    descriptions/
    operations/
    transport/
    actions/
    methods/
    helpers/
    interfaces/
    icons/
examples/
test/

Notes

Some execution endpoints, especially retry and stop, depend on the n8n version and deployment mode. The node wraps these calls with retries, timeouts, and user-friendly errors so unsupported endpoints fail clearly.

Hard Pause vs Normal Deactivate

n8n deactivate stops the production webhook or trigger from accepting new work, but it does not necessarily clear messages already held by an external provider. Providers such as Telegram or WhatsApp can store or retry events while a workflow is inactive and then deliver them after the workflow is activated again.

For activate, deactivate, bulk activate, bulk deactivate, maintenance mode, and graceful shutdown mode, Drop Events Received While Inactive defaults to on. With this hard-pause behavior, the node stores pause timestamps in global static data, updates dropBefore before reactivation, and attempts to purge stale new, running, and waiting executions for the target workflow.

Telegram supports clearing pending updates before activation. Select telegram as the trigger provider and provide the bot token; the node calls:

POST https://api.telegram.org/bot<TOKEN>/deleteWebhook

with:

{ "drop_pending_updates": true }

Generic webhooks and WhatsApp Cloud API retry queues cannot be cleared from n8n. For those providers, place Message Freshness Guard immediately after the trigger node, using a provider timestamp such as:

• Telegram: {{$json.message.date}}
• WhatsApp Cloud API: {{$json.entry[0].changes[0].value.messages[0].timestamp}}

The guard reads the selected workflow's dropBefore timestamp from static data. Events older than dropBefore return shouldProcess: false with reason: "event_before_last_activation"; fresh events return shouldProcess: true. For stricter production setups, use an always-on gateway that acknowledges paused webhook events with HTTP 200 and filters by timestamp or message ID.

Operational markers such as favorites, locks, and maintenance mode are represented with n8n tags:

• autoverse:favorite
• autoverse:locked
• autoverse:maintenance

Docker

Build a Docker image with the package installed into the official n8n image:

docker build -t autoverse-workflow-controller .

Examples

Example workflow JSON files are in examples/:

• health-dashboard.workflow.json
• bulk-maintenance.workflow.json
• execution-control.workflow.json

Import them into n8n, then select your own n8n API credential and workflows from the dynamic dropdowns.