Blueprints are pre-built workflow patterns that you can use as starting points. ORCFLO supports two types: Official blueprints maintained by the ORCFLO team, and User-published blueprints shared by the community.
Blueprint Types
The blueprint gallery contains two categories of blueprints, each with different characteristics.
| Type | Description | Examples |
|---|---|---|
| Official Blueprints | Created and maintained by the ORCFLO team. Vetted for quality, follow best practices, and are regularly updated. Show a "Verified" badge. | Customer Support Bot, Content Summarizer, Lead Qualification, Email Classifier |
| User-Published Blueprints | Created and published by ORCFLO users. Browse community contributions, use workflows others have built, or share your own creations. | Published by users, can be updated, can be unpublished |
Blueprint Badge
Official blueprints show a "Verified" badge in the gallery. User-published blueprints show the author's name and publish date.
Using Blueprints
Starting from a blueprint is the fastest way to build common workflows. Blueprints come pre-configured with nodes, connections, and sensible defaults.
Browse the blueprint gallery
Click "New Workflow" and select "From Blueprint" or navigate to the Blueprints page in the sidebar.
Filter and search
Filter by source (Official / Community / Featured) and category in the sidebar. Use the search bar to find blueprints by name, description, or tags.
Preview and select
Click a blueprint card to preview its structure, description, node count, and execution mode.
Create from blueprint
Click "Use Blueprint" to create a new workflow. This creates an independent copy you can modify freely.
Blueprint Independence
Workflows created from blueprints are independent copies. Changes you make won't affect the original blueprint or other users' copies.
Filtering & Discovery
The blueprint gallery provides a sidebar with source and category filters alongside full-text search, making it easy to find exactly what you need.
Source Filters
- All: Show every blueprint in the gallery
- Official: Blueprints maintained by the ORCFLO team - vetted for quality and best practices
- Community: User-published blueprints shared by the ORCFLO community
- Featured: Hand-picked highlights from both official and community sources
Categories
Blueprints are organized into broad use-case categories. Click a category in the sidebar to filter the gallery. Available categories include AI & LLMs, Content & Writing, Data & Analytics, Web Scraping, Developer Tools, and more.
Tags
When publishing, you can add up to 5 free-form hashtag-style tags to your blueprint (e.g., "slack", "summarization", "report"). Tags are searchable from the search bar, allowing fine-grained discovery.
Search is Tag-Aware
The search bar searches across blueprint names, descriptions, and tags. If you're looking for something specific, try searching by the tool or concept (e.g., "slack" or "pdf").
Media & Gallery
Great visuals help users understand what your blueprint does at a glance. The blueprint editor includes a media gallery where you can add screenshots, demo videos, and an interactive workflow canvas preview.
Adding Media
You have two options for adding images to your blueprint gallery:
- Upload your own:Click "Upload media" to add screenshots or demo videos directly from your computer. Images up to 5MB and videos up to 50MB are supported.
- Choose from defaults:Click "Choose defaults" to pick from a curated set of category-themed images. These are great when you want a polished look without creating custom graphics.
Make Your Blueprint Stand Out
Blueprints with gallery images get significantly more clicks in the explore page. Even a single default image is much better than no image at all.
Workflow Canvas
You can also include an interactive workflow canvas preview in the gallery. Toggle it on from the "Workflow Canvas" row in the media editor. Users can pan, zoom, and explore your workflow structure right from the blueprint detail page.
Tips
- You can add up to 6 media items and reorder them by dragging
- The first image in the gallery is used as the card thumbnail in the explore page
- Add captions to describe what each screenshot or video shows
- Mix default images with your own screenshots for the best presentation
Publishing Blueprints
Share your workflows with the community by publishing them as blueprints. Any workflow can be published as a user blueprint.
Open your workflow in the editor
Navigate to the workflow you want to publish.
Go to Settings > Sharing
Open workflow settings and navigate to the Sharing tab.
Click "Publish as Blueprint"
This starts the blueprint creation process from the Sharing panel.
Review the data confirmation
If your workflow contains uploaded files or verified emails, you'll see a confirmation that these will be removed from the blueprint copy before it is shared.
Customize in the Blueprint Editor
You'll be taken to the Blueprint Editor where you can customize your blueprint's name, subtitle, category, media gallery, badges, and more.
Fill in the required fields
At minimum, provide a name, category, and subtitle so users can understand what your blueprint does at a glance.
Click "Publish" to go live
When you're happy with how it looks, click "Publish" to make your blueprint visible in the gallery.
Save as a draft anytime
You can save as a draft at any time and come back later to finish. Drafts are private and not visible in the gallery until you publish.
Remove Sensitive Data
Before publishing, ensure you've removed any sensitive information like API keys, personal data, internal URLs, or proprietary prompts. Published blueprints are visible to all ORCFLO users.
Push Updates
After publishing, you can update your blueprint to incorporate improvements, fix issues, or add new features. Use "Push Update" to sync your latest workflow changes to the published blueprint.
- Make changes to your original workflow in the editor
- Click "Push Update" to sync changes to the published blueprint
- New users will get the updated version when they use the blueprint
- Existing workflows created from the blueprint are not affected
Version Independence
Push updates only affect the blueprint definition. Users who have already created workflows from your blueprint keep their independent copies unchanged.
Unpublishing
You can remove your blueprint from the public gallery at any time by unpublishing it. Unpublishing moves your blueprint back to draft — all your customizations are preserved and you can re-edit and republish whenever you're ready.
Open your published workflow
Navigate to the workflow that is currently published as a blueprint.
Click "Unpublish"
Find this in the workflow menu or the Share dropdown.
Confirm unpublish
Your blueprint is moved back to draft and removed from the public gallery. All your customizations — media, descriptions, and badges — are preserved so you can re-edit and republish at any time.
What Happens When You Unpublish
- Blueprint is removed from the gallery immediately and moved back to draft
- No new users can use the blueprint while it is in draft
- Existing workflows created from the blueprint continue to work
- All customizations (media, descriptions, badges) are preserved in the draft — nothing is lost
- You can re-edit and republish at any time from the Blueprint Editor
- For permanent removal, use the "Delete Blueprint" option instead of unpublishing
Best Practices
- Write clear descriptions: Explain what the blueprint does, required inputs, and expected outputs.
- Remove sensitive data: Clear API keys, personal info, and proprietary prompts before publishing.
- Test before publishing: Run your workflow with sample data to ensure it works correctly.
- Use meaningful names: Name nodes and steps descriptively so users understand the flow.
Common Mistakes to Avoid
| Mistake | Fix |
|---|---|
| Publishing with API keys | Always remove credentials before publishing. Use placeholder text like "YOUR_API_KEY" |
| Vague blueprint name | Use specific names: "Customer Support Email Classifier" not "Email Handler" |
| No description | Write a description explaining what the blueprint does, its inputs, and outputs |
| Forgetting to push updates | After fixing bugs, remember to push update so new users get the fix |