Block Inputs
How data flows into your workflows
Block Inputs
Block Inputs define what information a Block needs to do its work. Think of them as the fuel that powers each step in your Routine.
Document
Files, contracts, or reference materials the Block needs to analyze or draft from.
Input Form
Structured data collection fields for client intake or due diligence.
Prompt
Specific instructions constraining or guiding an AI-powered Block.
Dependent
Data from a previously completed Block in the Routine (e.g., using intake responses to populate a drafting step).
Blocks can also accept Document Field inputs (specific merge fields extracted from a document's metadata) and Report inputs (output from a previously generated report that feeds into a downstream Block).
Prompt Engineering
For AI-driven Blocks, your Prompt Input is critical. Never use vague prompts like "Review this contract."
Instead, use explicit directives: "Review this contract for indemnification clauses and flag any unlimited liability provisions. Pay special attention to data sovereignty constraints in Section 4."
When creating Forms, remember that the data collected is automatically available for all subsequent steps in that Routine, saving you from manual data entry.