Copy & Add to Library
Use community workflows in your projects.
Overview
There are two ways to use workflows from the Marketplace:
| Method | Your Copy | Customizable | Auto-Updates |
|---|---|---|---|
| Copy | Yes (full ownership) | Yes | No |
| Add to Library | No (reference only) | No | Yes |
Copy
Create your own copy of a workflow to customize.
When to Copy
- You need to modify the workflow
- You want full control over updates
- You're building on top of it
How to Copy
- Find a workflow in the Marketplace
- Click Copy
- Name your copy (optional)
- The workflow appears in your Library and Dashboard
After Copying
Your copy is completely independent:
- Edit steps, actions, and parameters
- Change adapter configurations
- Publish your own version (with attribution)
Original: bug-fix-workflow by @alice
↓ Copy
Your Copy: my-bug-fix-workflow by @youCopy Attribution
Copies maintain a link to the original:
{
"name": "My Enhanced Bug Fix",
"forkedFrom": {
"workflowId": "wf_abc123",
"userId": "alice",
"version": "1.2.0"
}
}Add to Library
Use a workflow without creating a copy.
When to Add to Library
- You want automatic updates
- You don't need customization
- You trust the maintainer
How to Add to Library
- Find a workflow in the Marketplace
- Click Add to Library
- Configure adapter settings (optional)
- The workflow appears in your Library
Managing Library Entries
In your Library, you can:
- Toggle workflows active/inactive
- Enable/disable specific adapters
- Reorder workflows
- Remove workflows you no longer need
Managing Your Library
View Library
Dashboard → Library shows:
- All workflows in your library
- Source type (owned or added from marketplace)
- Active status
- Enabled adapters
Toggling Active Status
Inactive workflows:
- Won't appear in deployments
- Won't be available in MCP endpoints
- Stay in your library for future use
Removing from Library
- Go to Dashboard → Library
- Find the workflow
- Click the menu → Remove from Library
Removing a workflow from your library will cause deployments using it to fail.
Copy vs Add to Library: Decision Guide
Do you need to customize the workflow?
├── Yes → Copy
└── No
└── Do you trust the maintainer?
├── Yes → Add to Library
└── Somewhat → Copy (to control updates)Example Workflow
Scenario: Using a Security Audit Workflow
- Browse Marketplace → Find "Security Audit Pro" by @securityteam
- Review → Check steps, ratings, recent updates
- Add to Library → Include in your library
- Create Deployment → Include in your MCP endpoint
- Use → Run security audits with automatic improvements
Later:
- Need Customization → Copy to add company-specific checks
- Maintain Both → Library entry for community updates, copy for custom rules
Best Practices
For Copying
- Credit the original author
- Document your changes
- Consider contributing back
- Keep your copy updated manually if needed
For Library Entries
- Review changelogs when workflows update
- Test updates in dev first
- Remove workflows you're not using
- Keep your library organized
Contributing Back
If you improve a copied workflow:
- Document your changes
- Contact the original author
- Offer to contribute via PR (if they accept)
- Or publish your enhanced version (with attribution)
Next Steps
- Browse the Marketplace
- Read the Marketplace Guide
- Learn about Publishing Workflows
- See Example Workflows