Forking & Subscribing

Use community workflows in your projects.

Overview

There are two ways to use workflows from the Marketplace:

Forking

Create your own copy of a workflow to customize.

When to Fork

• You need to modify the workflow
• You want full control over updates
• You're building on top of it

How to Fork

1. Find a workflow in the Marketplace
2. Click Fork
3. Name your forked copy
4. The workflow appears in your Dashboard

After Forking

Your fork is completely independent:

• Edit steps, actions, and parameters
• Change adapter configurations
• Publish your own version (with attribution)

Original: bug-fix-workflow by @alice
    ↓ Fork
Your Copy: my-bug-fix-workflow by @you

Fork Attribution

Forks maintain a link to the original:

{
  "name": "My Enhanced Bug Fix",
  "forked_from": {
    "workflow_id": "wf_abc123",
    "author": "alice",
    "version": "1.2.0"
  }
}

Subscribing

Use a workflow without creating a copy.

When to Subscribe

• You want automatic updates
• You don't need customization
• You trust the maintainer

How to Subscribe

1. Find a workflow in the Marketplace
2. Click Subscribe
3. Choose a version pin strategy
4. Add to a deployment

Version Pinning

Control which updates you receive:

Changing Version Pin

1. Go to Dashboard → Subscriptions
2. Find the subscription
3. Click Change Pin
4. Select new strategy

Managing Subscriptions

View Subscriptions

Dashboard → Subscriptions shows:

• Subscribed workflows
• Current version pin
• Latest available version
• Update status

Update Notifications

When a new version is available:

• In Dashboard - Badge on subscription
• Email - Optional notification
• Auto-update - Based on your pin

Unsubscribing

1. Go to Dashboard → Subscriptions
2. Click the subscription
3. Click Unsubscribe
4. Remove from deployments if needed

Fork vs Subscribe: Decision Guide

Do you need to customize the workflow?
├── Yes → Fork
└── No
    └── Do you trust the maintainer?
        ├── Yes → Subscribe (latest)
        └── Somewhat → Subscribe (^major or ~minor)

Combining Both

You can subscribe AND fork:

1. Subscribe to get updates
2. Fork when you need a custom version
3. Compare your fork with updates

Example Workflow

Scenario: Using a Security Audit Workflow

1. Browse Marketplace → Find "Security Audit Pro" by @securityteam
2. Review → Check steps, ratings, recent updates
3. Subscribe with ^2.0 pin (want updates, but not breaking changes)
4. Add to Deployment → Include in your project
5. Use → Run security audits with automatic improvements

Later:

6. Need Customization → Fork to add company-specific checks
7. Maintain Both → Subscribe for community updates, fork for custom rules

Best Practices

For Forking

• ✅ Credit the original author
• ✅ Document your changes
• ✅ Consider contributing back
• ✅ Keep your fork updated manually

For Subscribing

• ✅ Review changelogs before major updates
• ✅ Test updates in dev first
• ✅ Use appropriate version pins
• ✅ Set up update notifications

Contributing Back

If you improve a forked workflow:

1. Document your changes
2. Contact the original author
3. Offer to contribute via PR (if they accept)
4. Or publish your enhanced version (with attribution)

Next Steps

• Browse the Marketplace
• Read the Marketplace Guide
• Learn about Publishing Workflows
• See Example Workflows