Task inputs are the data that a task needs to run. We’ll show you how to define them.
task_inputs
field is used to define these relationships, effectively creating a Directed Acyclic Graph
(DAG) of task dependencies. This DAG
ensures that tasks are executed in the correct order, with each task receiving its required inputs only after they have been produced by preceding tasks.
input
to output
.graph
does not contain cycles, preventing infinite loops in task execution. That’s fancy way to say “we make sure your data doesn’t end up chasing its own tail.”network
structure.invoice_parsing
is the root node, with no dependencies.extract_customer_info
and extract_invoice_items
both depend on parsed_invoice
.create_invoice_qna
depends on both invoice_items
and customer_info
.