Building Workflows
Learn how to build automated workflows in Futurity.
Creating a New Workflow
Section titled “Creating a New Workflow”-
Navigate to Workflows
Click Workflows in the dashboard sidebar.
-
Click Create Workflow
Click the + Create button in the top right.
-
Name your workflow
Give it a descriptive name like “Weekly Sales Report” or “New Lead Processing”.
-
Open the builder
You’ll see the visual workflow canvas.
The Workflow Canvas
Section titled “The Workflow Canvas”Navigation
Section titled “Navigation”- Pan: Click and drag on empty space
- Zoom: Scroll or use zoom controls
- Select: Click on nodes
- Multi-select: Shift+click or drag a selection box
Adding Nodes
Section titled “Adding Nodes”- Click the + button or drag from the node palette
- Choose the node type
- Position on the canvas
- Configure the node settings
Connecting Nodes
Section titled “Connecting Nodes”- Hover over a node to see connection points
- Drag from an output point to an input point
- The connection line shows data flow direction
Building a Simple Workflow
Section titled “Building a Simple Workflow”Let’s build a workflow that analyzes daily data.
-
Create a new workflow
- Click + Create in Workflows
- Name it “Daily Data Analysis”
- Select Scheduled trigger type
-
Add an Agentic Node
- Drag an Agentic node onto the canvas
- Configure the task:
Task Name: Analyze daily metricsTask Description: Summarize the key activities from yesterday including:- New tasks created- Tasks completed- Any blockers or issuesKeep it concise, under 200 words. -
Add another Agentic Node
- Drag another Agentic node
- Connect it to the first node
- Configure it to save results to Vault
-
Save and Test
- Click Save
- Test the workflow with sample data
- Verify the output
-
Publish
- Toggle the workflow to Published
- It will run on the configured schedule
Working with Variables
Section titled “Working with Variables”Node Context
Section titled “Node Context”Data flows between nodes through context:
- Each node receives context from previous nodes
- Nodes can access outputs from predecessor nodes
- Context is passed automatically through the graph structure
Error Handling
Section titled “Error Handling”Workflows automatically handle errors:
- Failed nodes are logged in the execution history
- You can view error details in the run history
- Workflows can continue past failed nodes if configured
Testing Workflows
Section titled “Testing Workflows”Test Mode
Section titled “Test Mode”Click Test to run the workflow with:
- Sample trigger data
- Mock external services (optional)
- Real-time execution visibility
Test Data
Section titled “Test Data”Provide test data in JSON format:
{ "customer_name": "Acme Corp", "order_total": 1500, "items": ["Widget A", "Widget B"]}Debugging
Section titled “Debugging”During test runs, you can see:
- Each node’s input and output
- Execution time per node
- Errors and their details
Best Practices
Section titled “Best Practices”- Name nodes descriptively: “Fetch customer data” not “HTTP 1”
- Add comments: Document complex logic
- Test incrementally: Build and test in stages
- Handle errors: Always plan for failure cases
- Monitor after launch: Watch the first few executions
Saving and Versioning
Section titled “Saving and Versioning”- Auto-save: Changes are saved automatically
- Version history: Access previous versions from workflow settings
- Duplicate: Create a copy to experiment without affecting the original