Workflows orchestrate the actual execution of document generation and e-signature processes with specific participants and data. You can create workflows in three ways: instantiate from a blueprint (reusable process definition), create from a template (single document with steps), or build from scratch programmatically by defining documents, participants, and steps directly.

Each workflow contains documents (rendered PDFs populated with entity data), participants (real people assigned to roles), entities (structured data objects that populate document fields), and a step execution tree (tracking progress through the process). Workflows are one-time executions tied to specific transactions. For example, creating a workflow for a real estate purchase with buyer John Doe and seller Jane Smith tracks that specific property transaction from document generation through signing to completion.

Workflows progress through statuses (Pending, InProgress, Completed, Failed) as steps execute. Steps can be groups orchestrating child steps in parallel or sequential execution, or participant tasks where assigned users review and sign documents. You can monitor workflow progress in real-time and execute workflows programmatically, with participant tasks pausing execution until users complete their actions.