Writing Good Node Instructions
Node instructions are the single most important control you have over workflow behavior.
What to include
Goal: What should this node accomplish?
Inputs: What should it use from upstream nodes or context?
Output format: Bullet list, table, JSON, a short summary, etc.
Constraints: What to avoid, what to prioritize, and what to do when information is missing.
Patterns that work well
Make the node’s job “single-purpose”
Prefer:
“Search for the relevant workbook and return the workbook/worksheet link.”
Over:
“Search, read, analyze, write a report, and respond.”
Tell it where to put results
If you plan to use downstream nodes, ask for explicit structure:
“Return the top 3 candidate workbooks and explain why each matches.”
“Include a short ‘Next step’ recommendation for downstream actions.”
Provide a template when needed
For example, in Create Report:
## Summary
{{INSERT IMAGE: chart of ...}}
## Findings
- ...
## Recommendations
- ...
Anti-patterns to avoid
Vague instructions: “Help me with this.”
Multi-step prompts that belong in multiple nodes.
Assuming context: If a workbook/worksheet matters, attach a Seeq context or ask the workflow to find one.