All workflow step types — Person, Department, Parallel, Timer, Notification, and more.
DocQ provides 17 step types that cover a wide range of workflow actions — from simple approvals and signatures to HTTP calls, document transformations, and third-party integrations. This page covers the common settings shared across step types, followed by a detailed description of each type.
Most step types share the following configuration options.
You can assign a custom name to any step. While optional, custom names improve readability on the canvas, especially in workflows with many steps of the same type.
Each step can be configured to notify users when a document enters or leaves the step. Notifications are sent via email and appear in the DocQ notification center.
For steps that involve document review, you can require an e-signature in addition to the standard review action. This is configured per destination by enabling the Require signature on approval checkbox in the step settings.

For details on configuring signature templates, see Signature Templates.
When a document template is associated with the workflow (via Workflow Settings), you can insert template variable values into the email subject and body of step notifications. To use variables:

When a step targets an external user (someone without a DocQ account), you can dynamically populate the recipient's name and email from template variables rather than entering them manually:

Assigns the task to a specific person — either a DocQ user or an external user (identified by name and email). Configuration options include:
Assigns the task to a department. Any user within the specified department can act on the document. Configuration options include:
Assigns the task to a user with a specific role. The first user holding that role who acts on the document moves it forward. A signature can be required.
Submits the document to another workflow as a sub-process. The document enters the target workflow, progresses through its steps, and returns to the originating workflow once the sub-workflow completes.
Integrates with DocuSign for external signature collection. Users from the previous step are sent the document for signing through DocuSign. The workflow pauses until all required DocuSign signatures are collected.
Creates one or more new documents from specified page ranges of the original document and submits each to a selected workflow. The original document continues through the current workflow independently.
To configure a split:
Assigns the task to multiple targets (persons, departments, or roles), but only one of the specified targets needs to act for the document to advance. This differs from the Parallel step, which requires all targets to act.
Assigns the task to multiple targets (persons, departments, or roles), and all specified targets must act before the document advances.

Configuration options include:
Provides read-only access to a form with its metadata values displayed. The recipient can view the form data but cannot modify it.
Sends a form to a recipient via email. When the recipient completes and submits the form, a new document is created and attached to (or replaces) the main document in the workflow.
Configuration options include:
Sends an advanced notification email without requiring any action from the recipient. This step is useful for informing stakeholders about a document's progress.
Makes an HTTP call to an external service when the document reaches this step. Use this for integrations with systems that expose REST or HTTP APIs.
Configuration options include:
Performs automated property changes on the document without user interaction. Available operations include:
Performs automated content changes on the document without user interaction. Available operations include:
Introduces a delay before the workflow advances to the next step. The delay can be defined in two ways:
Enables integration with third-party systems through pre-built plugins. The available operations depend on which plugins are configured in your DocQ environment. See Integrations Overview for available integrations.
Dynamically specifies the target person, department, or role using template variable values rather than a fixed assignment. This allows the workflow to route documents to different users based on the document's own data — for example, routing to a manager whose name is captured in a form field.