Blueprint Format Spec
Everything you need to know about creating and formatting workflow blueprints for FlowForge.
What is a Blueprint?
A blueprint is a structured, reusable workflow template for AI agents and automation platforms. It includes trigger definitions, step-by-step instructions, and output specifications that buyers can import and deploy in their own systems.
Blueprint Structure
Every blueprint on FlowForge contains these required sections:
Metadata
Name, tagline, description, category, tags, and pricing. This is what buyers see in search results and browse pages.
Platform Targets
Which platforms the blueprint works with: Zapier, Make, n8n, OpenAI, or custom API. Buyers filter by platform, so accuracy is critical.
Workflow Steps
A numbered sequence of actions. Each step includes a title, description, trigger type (event/action/condition/transform), and optional platform reference.
Trigger Definition
What event or condition starts this workflow. Examples: new email received, form submitted, scheduled time, webhook received.
Output Sample
A JSON example of what the workflow produces. This helps buyers understand exactly what they're getting and verify the workflow fits their needs.
Complexity & Setup Time
Self-assessed complexity level (beginner/intermediate/advanced) and estimated setup time. Honest assessments build trust and reduce refund requests.
Blueprint Schema
{
"slug": "unique-slug-id",
"name": "Blueprint Name",
"tagline": "One-sentence description",
"description": "Full markdown description...",
"category": "customer-support | sales-automation | research-analysis | meeting-prep | hr-recruiting | data-extraction | devops",
"price": 4900,
"creator": {
"name": "Creator Name",
"handle": "@handle or https://site.com"
},
"tags": ["tag1", "tag2"],
"platformTargets": ["zapier", "make", "n8n", "openai", "custom-api"],
"complexityLevel": "beginner | intermediate | advanced",
"estimatedSetupMinutes": 45,
"workflowSteps": [
{
"stepNumber": 1,
"title": "Step Title",
"description": "What this step does",
"triggerType": "event | action | condition | transform",
"platform": "optional-platform"
}
],
"trigger": {
"type": "webhook | schedule | crm | email",
"description": "What starts this workflow"
},
"outputSample": "{ key: value }",
"iconEmoji": "🎯",
"iconGradient": "linear-gradient(...)",
"version": "1.0.0"
}Workflow Step Types
Each step in your workflow should be classified by its type:
Something that happens externally and triggers the workflow: new email, webhook received, scheduled time, form submission.
A task performed by the workflow: call an API, send a message, update a record, query a database.
A branching decision: if/else logic, filtering, checking thresholds. The workflow path changes based on this.
Data processing: parsing, formatting, mapping fields, combining sources, generating output.
Submission Guidelines
Be Specific
Generic workflows like "send an email" are less valuable than specific ones like "send a Slack DM to the #sales channel with lead score and company name in the message."
Include Real Examples
Use real trigger examples (e.g., "Zendesk ticket created") rather than generic ones ("new record"). Buyers need to know this will work in their setup.
Test Before Submitting
Your blueprint should work as described. Include enough detail that a competent user can deploy it without asking you questions.
Price Fairly
We recommend $29-$79 for most workflows. Complex, multi-step workflows can go higher. Consider the time savings you're delivering relative to building from scratch.
Need Help?
Have questions about creating your blueprint? Contact us or check the FAQ in our community forum.
Submit Your Blueprint