Glossary
Definitions for terms used across ForgeWorkflows product pages, documentation, and quality standards.
BQS v2 (Blueprint Quality Standard)
A 12-point quality audit applied to every ForgeWorkflows Logic Blueprint before it is listed for sale. BQS v2 evaluates error handling, documentation completeness, node configuration, credential isolation, and architectural consistency. A blueprint must pass all 12 points to be listed. No exceptions, no partial passes.
Dead Letter Logger
An error-handling pattern used in ForgeWorkflows blueprints. When a workflow step fails, the Dead Letter Logger captures the failed payload, the error message, and the timestamp, then routes it to a designated log destination instead of silently dropping the record. This ensures no data is lost during processing failures.
ITP (Independent Test Protocol)
A product-specific suite of test milestones that every ForgeWorkflows blueprint must pass before release. ITP covers live smoke tests with real API calls, edge-case handling, consistency scoring across multiple runs, and cost verification. Milestone counts vary by product complexity. Results are published on every product page in the Technical Reference section.
Lead Utility Score
An ICP (Ideal Customer Profile) scoring framework used by several ForgeWorkflows prospecting and qualification blueprints. The score evaluates leads against configurable criteria such as company size, industry fit, technology stack, and engagement signals. The output is a numeric score with a structured rationale, not a binary pass/fail.
Logic Blueprint
A production-grade n8n workflow package sold by ForgeWorkflows. Each Logic Blueprint is a complete, tested automation system that the customer owns outright after a one-time purchase. Blueprints include the workflow JSON, a setup guide, credential configuration instructions, and published ITP test results. There is no subscription, no vendor lock-in, and no API middleman.
Modular Agentic Swarm
The architecture pattern used in ForgeWorkflows blueprints. Instead of a single monolithic workflow, each blueprint is composed of specialized agent steps that handle distinct tasks — research, scoring, formatting, delivery — and pass structured data between them. This modular design allows individual agents to be updated or replaced without rebuilding the entire workflow.
n8n
An open-source workflow automation engine that serves as the runtime for all ForgeWorkflows Logic Blueprints. n8n can be self-hosted on your own infrastructure or used via n8n Cloud. ForgeWorkflows blueprints are tested against n8n version 2.11.2 and above. The customer deploys blueprints on their own n8n instance — ForgeWorkflows does not host or run workflows on your behalf.
Signed URL
A time-limited download link generated after a successful purchase. Signed URLs allow the buyer to download their Logic Blueprint securely without requiring an account or login. The link expires after a set period for security. If the link expires, the buyer can request a fresh download link via support.
Tier 1 / Tier 2 / Tier 3 LLM
A classification system for how ForgeWorkflows blueprints use large language models. Tier 1 (Reasoning) handles complex analysis, multi-step logic, and structured output generation. Tier 2 (Classification) handles categorization, scoring, and pattern matching at lower cost. Tier 3 (Creative) handles text generation such as email drafts and summaries. Each blueprint documents which tier is used at each agent step, so the customer understands cost and capability tradeoffs.
Webhook Trigger
A workflow activation method where an external system sends an HTTP request to your n8n instance to start the workflow. This is the real-time trigger pattern used by most ForgeWorkflows blueprints — the workflow runs immediately when new data arrives. The alternative is a schedule trigger, which polls for new data at set intervals. Each blueprint documents which trigger type it uses.