Templates

Last updated: Jan 2026

Templates are pre-built workflow patterns that you can use as starting points. ORCFLO supports two types: Official templates maintained by the ORCFLO team, and User-published templates shared by the community.

Template Types

The template gallery contains two categories of templates, each with different characteristics.

TypeDescriptionExamples
Official TemplatesCreated 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 TemplatesCreated 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

Template Badge

Official templates show a "Verified" badge in the gallery. User-published templates show the author's name and publish date.

Using Templates

Starting from a template is the fastest way to build common workflows. Templates come pre-configured with nodes, connections, and sensible defaults.

1

Browse the template gallery

Click "New Workflow" and select "From Template" or navigate to the Templates page in the sidebar.

2

Filter by type and role

Toggle between "Official" and "User Published" tabs. Search by name, filter by category, or filter by target role to find templates designed for your job function.

3

Preview and select

Click a template card to preview its structure, description, node count, and execution mode.

4

Create from template

Click "Use Template" to create a new workflow. This creates an independent copy you can modify freely.

Template Independence

Workflows created from templates are independent copies. Changes you make won't affect the original template or other users' copies.

Role-Based Filtering

Templates can be tagged with a target role to help users find workflows designed for their specific job function. This makes it easier to discover relevant templates without searching through the entire catalog.

How Role Filtering Works

  • Filtering by role: Use the role filter in the template gallery to view only templates designed for your job function (e.g., Executive, Product Manager, Software Engineer)
  • Role badges: Templates with a target role display a role badge on their card, making them easy to identify at a glance
  • Optional field: Templates without a target role are still visible when "All Roles" is selected
  • Combine filters: Use role filtering alongside category and source filters for more precise results

Setting a Target Role

When publishing or editing a template, you can optionally specify a target role from the predefined list. This helps users in that role find your template more easily.

When to Use Role Tags

Add a target role when your template is specifically designed for users in a particular job function. For example, "Executive Dashboard" would be tagged for Executives, while "Code Review Automation" would be tagged for Software Engineers. Leave it blank if your template is universally applicable.

Publishing Templates

Share your workflows with the community by publishing them as templates. Any workflow can be published as a user template.

1

Open your workflow

Navigate to the workflow you want to publish in the editor.

2

Click "Publish as Template"

Find this option in the workflow menu (three dots) or the Share dropdown.

3

Add metadata

Provide a name, description, category, and optionally a target role for your template. The target role helps users find templates designed for their job function (e.g., Executive, Software Engineer). Good descriptions help users understand what the template does.

4

Confirm publish

Your template is now available in the "User Published" section of the template gallery.

Remove Sensitive Data

Before publishing, ensure you've removed any sensitive information like API keys, personal data, internal URLs, or proprietary prompts. Published templates are visible to all ORCFLO users.

Push Updates

After publishing, you can update your template to incorporate improvements, fix issues, or add new features. Use "Push Update" to sync your latest workflow changes to the published template.

  • Make changes to your original workflow in the editor
  • Click "Push Update" to sync changes to the published template
  • New users will get the updated version when they use the template
  • Existing workflows created from the template are not affected

Version Independence

Push updates only affect the template definition. Users who have already created workflows from your template keep their independent copies unchanged.

Unpublishing

You can remove your template from the public gallery at any time by unpublishing it.

1

Open your published workflow

Navigate to the workflow that is currently published as a template.

2

Click "Unpublish"

Find this in the workflow menu or the Share dropdown.

3

Confirm unpublish

The template is removed from the public gallery. Your workflow remains in your account.

What Happens When You Unpublish

  • Template is removed from the gallery immediately
  • No new users can use the template
  • Existing workflows created from the template continue to work
  • Your original workflow is not deleted
  • You can republish the same workflow later

Best Practices

  1. Write clear descriptions: Explain what the template does, required inputs, and expected outputs.
  2. Remove sensitive data: Clear API keys, personal info, and proprietary prompts before publishing.
  3. Test before publishing: Run your workflow with sample data to ensure it works correctly.
  4. Use meaningful names: Name nodes and steps descriptively so users understand the flow.

Common Mistakes to Avoid

MistakeFix
Publishing with API keysAlways remove credentials before publishing. Use placeholder text like "YOUR_API_KEY"
Vague template nameUse specific names: "Customer Support Email Classifier" not "Email Handler"
No descriptionWrite a description explaining what the template does, its inputs, and outputs
Forgetting to push updatesAfter fixing bugs, remember to push update so new users get the fix