Node Types
Start Node
The Start node is the entry point for the workflow. Duckie creates it automatically when you create a workflow. Outputs:- Next — Begins workflow execution
Tool Node
Executes a tool or another reusable resource. Configuration:
Outputs:
- Success — Tool executed successfully
- Failure — Tool execution failed
- Search company docs
- Send a response with the Responder tool
- Call a custom API
- Call a tool from an MCP server
- Call another agent as a sub-agent
- Run a runbook or another workflow
- Create a Jira ticket or update a Zendesk ticket
Decision Node
Routes the workflow across branches. Branches are evaluated from top to bottom. The first matching branch is taken; if no branch matches, the Else path is taken. Configuration:
Outputs:
- One output per branch
- Else fallback output
End Node
Marks a workflow path as complete.Condition Reference
Decision branches can use a Rule condition or an AI condition.Rule Conditions
Rule conditions compare a selected value against another value.
Available comparisons:
AI Conditions
AI conditions use a prompt and selected inputs to make a judgment.
Example prompt:
Input Mapping
Use input mapping to pass values into tool parameters and conditions.Best Practices
Node Naming
- Use descriptive names: “Check order eligibility” not “Decision 1”
- Include the action: “Lookup order in database”
- Be consistent across workflows
Error Handling
- Always connect Failure outputs
- Provide fallback paths for errors
- Consider retry logic for transient failures
Testing
- Test each path through the workflow
- Verify variable mapping works correctly
- Check edge cases and error conditions
Next Steps
Create Workflows
Build workflows using these nodes
Tools Reference
See available tools for Tool nodes