Frequently Asked Questions

You receive a downloadable bundle containing the n8n workflow JSON file, a step-by-step README, an Error Handling Matrix documenting all failure modes, and a Blueprint Dependency Matrix listing every service and credential required. The exact contents vary by product and are listed on each product page under "What’s Inside."

After payment, you are redirected to a confirmation page with a secure, time-limited download link (a signed URL). You also receive an email with the same link. If the link expires, contact support@forgeworkflows.com for a fresh download link.

No. The download link is a signed URL that expires after a set period. Import the workflow by downloading the .json file to your computer first, then using n8n’s "Import from File" option. The README in your bundle walks through this step by step.

All sales are final after download. These are digital goods — once downloaded, the blueprint cannot be returned. Review the Blueprint Dependency Matrix and prerequisites on the product page before purchase. Questions? Contact support@forgeworkflows.com before buying. Full terms at /legal.

All blueprints are tested against n8n version 2.11.2 and above. If you are running an older version, we recommend upgrading before importing. The n8n version requirement is listed on every product page under "What You’ll Need."

No. Blueprints work on both self-hosted n8n and n8n Cloud. Self-hosted gives you full control over data and infrastructure. n8n Cloud is a managed option if you prefer not to maintain a server. Either way, you deploy the blueprint on your own instance.

Each product page lists the exact credentials required under "What You’ll Need." Common requirements include an Anthropic API key (used by all blueprints) and CRM credentials (HubSpot, Pipedrive, etc.). The Blueprint Dependency Matrix in each bundle documents every service, estimated cost, and where to obtain the key.

Each blueprint includes a README designed for setup in under 10 minutes: import the workflow JSON, configure API credentials, customize the configuration for your use case, and run a test record. The "What You’ll Need" section on each product page shows a setup track estimate — Quick Start (~15 min if you have all credentials ready), Full Setup (1–2 hours including API configuration), or From Scratch (2–4 hours if starting without n8n).

A Logic Blueprint is a production-grade n8n workflow package. Each one is a complete, tested automation system that you own outright after a one-time purchase. It includes the workflow JSON, setup documentation, error handling documentation, and published test results. There is no subscription, no vendor lock-in, and no API middleman. See the full definition in our glossary.

It is the architecture pattern used in all ForgeWorkflows blueprints. Instead of a single monolithic workflow, each blueprint is composed of specialized agent steps — research, scoring, formatting, delivery — that pass structured data between them. This modular design allows individual agents to be updated or replaced without rebuilding the entire workflow. See the full definition in our glossary.

Yes. Every blueprint is a standard n8n workflow JSON file that imports into any n8n instance — self-hosted or Cloud. No proprietary nodes, no custom plugins, no platform lock-in.

Yes. You own the workflow file. You can modify any node, change the logic, swap integrations, adjust prompts, or extend the pipeline. The workflow runs on your n8n instance — you have full access to everything.

BQS v2 (Blueprint Quality Standard version 2) is a 12-point quality audit applied to every blueprint before it is listed for sale. It evaluates error handling, documentation, architecture, prompt engineering, data schemas, export verification, and more. A blueprint must pass all 12 points — no exceptions. Read the full standard at /methodology/bqs.

The ITP (Independent Test Protocol) is a product-specific suite of test milestones covering live smoke tests, edge cases, consistency scoring, and cost verification. Milestone counts vary by product complexity. All results are published on every product page in the Technical Reference section. Nothing is estimated — every number comes from a real test run. Read the full methodology at /methodology/itp.

Cost-per-record figures published on product pages are measured from actual ITP test runs, not projected. However, actual costs depend on your input data, API pricing (which providers can change), and how you configure the blueprint. Published figures represent what we measured during testing and are intended as a reliable baseline, not a guarantee.