Copy and Customize Any Workflow
Learn how to copy public workflows, understand provenance tracking, work with variables, and master flow control with toggles and sequences.
Copy and Customize Any Workflow
One of FlowDot's most powerful features is the ability to copy any public workflow and make it your own. This deep-dive tutorial covers copying, customization, and advanced editor techniques.
What You'll Learn
- Copy public workflows to your account
- Understand workflow provenance (history)
- Work with variables and the Set Variable node
- Control flow with toggles and sequence dependencies
- Clean up and optimize workflows
Part 1: Copying Workflows
Finding Public Workflows
- Click the FlowDot logo (top left) to go to the Search page
- Browse by category or search for keywords
- Click any workflow to see details
Copying a Workflow
When viewing a public workflow you don't own:
- Click Edit in the dashboard
- You'll see: "This workflow belongs to someone else"
- Click Copy to My Workflows
- The workflow is now yours to edit!
Note: Shared keys from the original designer are not copied. You'll need to provide your own.
Part 2: Understanding Provenance
FlowDot tracks the history of copied workflows.
Viewing Provenance
- Open your copied workflow
- Click Settings (gear icon)
- Look for the Provenance section
You'll see a chain like:
Original: FlowDot Official
└→ Copied by: YourUsername (this workflow)
Why Provenance Matters
- Credit original creators
- Track workflow evolution
- Find the source for updates
- Community attribution
Part 3: Working with Variables
Variables let you store and reuse values throughout a workflow.
The Set Variable Node
- Open Variables category
- Drag Set Variable onto the canvas
- Configure:
- Variable Name: e.g.,
city_name - Value: Connect an input or set directly
- Variable Name: e.g.,
Using Variables in Text
Reference variables with single curly braces:
The weather in {city_name} is {temperature} degrees.
Variable vs User API Key Syntax
| Syntax | Type | Example |
|---|---|---|
{variable} |
Workflow variable | {city_name} |
{{api_key}} |
User API key | {{open_weather_key}} |
Part 4: Flow Control
Sequence Dependencies
Sometimes nodes must run in a specific order.
The Problem: Variables need to be set before they're used.
The Solution: Sequence dependencies (dotted lines)
- Right-click a node > Properties
- Find Sequence After
- Select the node that must complete first
- A dotted line shows the dependency
Example:
[Set State Variable] -----> [Set City Variable] -----> [HTTP Request]
(1) dotted (2) dotted (3)
The HTTP Request waits for both variables to be set.
The Toggle Node
Toggles let you enable/disable parts of your workflow.
- Open Flow Control category
- Drag a Toggle node onto the canvas
- Connect input on left, output on right
- Set the toggle On or Off
When On: Data passes through When Off: Data is blocked
Use Cases:
- Disable expensive LLM calls during testing
- Create A/B test branches
- Add optional post-processing
Part 5: Cleaning Up Workflows
Copied workflows often have extra nodes you don't need.
Removing Unnecessary Nodes
- Select the node
- Press
DeleteorBackspace - Connections are automatically removed
Common Nodes to Remove After Copying
| Node | Why Remove |
|---|---|
| Shared Keys | You'll use your own keys |
| Notice/Thought Bubble | Designer notes, not needed |
| Debug Outputs | Only useful during development |
Reorganizing the Canvas
- Select multiple nodes:
Shift+Clickor drag a selection box - Move them together
- Keep data flowing left-to-right
- Group related nodes together
Part 6: Customization Walkthrough
Let's walk through customizing a weather workflow:
Original Workflow
[City Input] -> [Set City Variable] -> [Build URL] -> [HTTP Request] -> [LLM Summary] -> [Output]
[State Input] -> [Set State Variable] --^
Customization Steps
-
Remove Shared Keys node (we'll use our own)
-
Update the Key Requirements node:
- Header: "You need this key"
- Key:
open_weather_key - Link: openweathermap.org
- Info: "Free tier available"
-
Simplify the URL construction:
- Instead of multiple Set Variable nodes
- Use direct reference:
q={{city}},{{state}}&appid={{open_weather_key}}
-
Add your personal touch:
- Change the LLM system prompt
- Adjust output formatting
- Add additional processing
-
Test thoroughly:
- Run with different inputs
- Check error handling
- Verify all paths work
-
Save your version:
- Give it a new name
- Update the description
- Optionally make it public
Pro Tips
Debugging Workflows
- Click any node to see its current output
- Add Text Output nodes temporarily to inspect values
- Use the Toggle to isolate sections
- Check execution history for past results
Performance Optimization
- Minimize LLM calls - they're the slowest
- Use Simple tier for preprocessing
- Batch operations when possible
- Cache results with variables
Sharing Your Customizations
Once your workflow works well:
- Update the description to explain your changes
- Add a Key Requirements node if needed
- Set visibility to Public
- Share the link with the community!
Summary
Copying and customizing workflows lets you:
- Learn from community examples
- Build on proven patterns
- Avoid starting from scratch
- Contribute improvements back
Key techniques:
- Use variables for reusable values
- Set sequence dependencies for order control
- Toggle sections for testing
- Clean up unnecessary nodes
Next, learn about the AI Agent and how to give it access to your workflows!