Workflow Library

1,340 real n8n workflows converted to QuoxFlow format. 154 are ready to run today; the rest are browsable references you adapt.

Overview

The Workflow Library plugin ships with 1,340 workflow templates converted from a real n8n workflow archive into QuoxFlow format. 154 of those convert cleanly or with only minor polish and are ready to run today; the rest are complete, browsable workflow definitions you can inspect, copy the JSON of, and adapt as a starting point once the node types or connectors they need are covered.

Templates cover a wide range of integrations, including Slack, OpenAI, Google Sheets, GitHub, Telegram, Discord, and many others. Every template includes metadata such as node count, complexity rating, integration badges, and AEE safety indicators.

The plugin is available on the free tier. No configuration is required beyond enabling it in the plugin registry.

Node-type coverage varies by template. QuoxFlow's n8n converter maps a growing set of vendor integrations (Slack, Telegram, Gmail, Google Sheets, Google Drive, Airtable, Notion, email send, and OpenAI) to real, runnable calls, plus n8n's Agent and Chain nodes onto QuoxFlow's own agent system.

Some templates convert and run with no further edits; most need some manual configuration, most commonly wiring up a node type outside the converter's current coverage, or setting a credential variable. See the QuoxFlow docs page for current conversion numbers.

Browsing Templates

The library offers two view modes:

• Grid view displays templates as cards, each showing the workflow name, a short description, integration badges, node count, and a complexity indicator. This is the default view and works well for visual scanning.
• List view presents templates in a compact table format with sortable columns. This is more efficient when you already know roughly what you are looking for.

Each template card or row includes:

• Workflow name and description
• Node count (total nodes in the workflow)
• Integration badges (icons for each connected service)
• Complexity indicator (simple, moderate, advanced)
• AEE safety rating and DEFCON level indicator
• Category tag

You can switch between grid and list views at any time without losing your current search or filter state.

Search and Filtering

The search bar accepts queries against multiple fields simultaneously: workflow name, description, integration name, and tags. Results update as you type.

Filters can be combined:

• Category -- narrow results to a specific workflow category (see Categories below)
• Integration -- show only templates that include a particular service (e.g. "OpenAI" or "GitHub")
• Complexity -- filter by simple, moderate, or advanced
• Tags -- filter by any tag attached to the template metadata

All filters are additive. Selecting "AI/LLM" as the category and "OpenAI" as the integration returns only AI/LLM workflows that use the OpenAI integration.

Search results preserve the selected view mode (grid or list) and can be further refined by adding or removing filters without clearing the text query. The result count is displayed alongside the search bar so you can gauge the scope of your current filter set.

WireMap Diagrams

Each template includes a WireMap diagram rendered with React Flow. WireMap is the visual representation format used by QuoxFlow to describe workflow topology: nodes, edges, and data flow between steps.

The diagram view shows:

• Each node as a labelled block with its integration icon
• Directional edges indicating execution order and data flow
• Conditional branches and parallel paths where applicable
• Entry and exit points

Diagrams are read-only in the library context. To edit a workflow's topology, deploy it first and open it in the QuoxFlow editor.

For larger workflows with many nodes, the diagram supports pan and zoom controls. Node labels remain readable at all zoom levels, and edges are routed to minimise visual overlap.

Template Format

Every workflow template is stored as a JSON document conforming to the QuoxFlow schema. The key fields are:

You can inspect the raw JSON for any template by selecting "View raw JSON" from the template detail view.

The aee field contains the AEE envelope metadata used by QuoxCORE for policy enforcement and audit logging. The defcon field is an integer from 1 to 5, where 1 indicates lowest operational risk and 5 indicates highest. Both fields are computed automatically during template validation.

Categories

Templates are organised into four primary categories:

AI/LLM

Workflows that involve language models, embeddings, classification, summarisation, or other AI-driven steps. Examples include multi-model chaining, RAG pipelines, content generation flows, and sentiment analysis pipelines. Many of these templates are designed to work with multiple LLM providers, so you can swap the model backend without restructuring the workflow.

Automation

Task automation workflows such as scheduled data processing, file management, cron-triggered jobs, and system maintenance routines. These typically run unattended on a schedule or in response to system events. Common patterns include periodic health checks, log rotation triggers, and batch data transforms.

Integration

Workflows focused on connecting two or more external services. Examples include syncing data between Google Sheets and a database, mirroring GitHub issues to a project tracker, forwarding webhook payloads between APIs, and maintaining bidirectional sync between CRM and support platforms.

Communication

Workflows that send, receive, or route messages across platforms. Slack notifications, Telegram bots, Discord alerts, email digests, and multi-channel broadcast patterns fall into this category. Several templates support conditional routing, where the destination channel is selected based on message content or priority level.

Using Templates

There are three ways to use a template from the library:

Copy Workflow ID

Every template has a unique ID. Copy it to reference the template in API calls, CLI commands, or QuoxFlow configuration files.

Use as Template

Select "Use as template" to create a new workflow in your QuoxCORE instance based on the template. This copies the full workflow definition into your workspace, where you can modify nodes, change integrations, and adjust configuration before activating it.

The original template is not affected by any changes you make to your copy. You can create multiple workflows from the same template, each with different configurations for different environments or use cases.

View Raw JSON

Opens the complete JSON definition of the template. This is useful for reviewing the exact node configuration, understanding edge conditions, or importing the workflow into external tooling.

AEE Indexing and Safety

All templates are indexed with AEE (Agent Envelope Exchange) metadata. This includes:

• A safety rating derived from the operations each node performs (read-only, write, delete, external API call)
• A DEFCON level indicator reflecting the operational risk profile of the workflow as a whole
• Envelope metadata that enables QuoxCORE to enforce policy checks before activation

Templates with higher risk ratings (e.g. those that delete records or call external APIs with write permissions) are flagged accordingly. Review the safety rating and DEFCON level before deploying any template into a production environment.

Notes

• The Workflow Library is a read-only catalogue. You cannot edit templates in place. Use "Use as template" to create a mutable copy in your workspace.
• Templates that require specific integrations will not activate unless those integrations are configured in your QuoxCORE instance. The template detail view lists all required integrations so you can verify availability before deploying.
• Workflow IDs are stable across releases. You can reference them in scripts, API calls, and documentation without worrying about them changing between versions.
• The complexity indicator is calculated from the number of nodes, the number of conditional branches, and whether the workflow includes external API calls. It is informational only and does not restrict deployment.
• WireMap diagram data is included in the template JSON under the wireMap field. If you import a template via the API rather than the UI, the diagram layout will be preserved.
• Templates are not automatically re-validated or removed on release. Run-readiness varies by template: as of the last audit, 154 of 1,340 convert to a working QuoxFlow workflow with no edits or only a credential variable to fill in; the rest are complete, browsable references you can inspect and adapt as connector and node-type coverage grows. The template detail view shows current status; see the QuoxFlow solutions page for the full breakdown.