Process Street workflow templates and checklist creation
Workflow templates are the foundation of Process Street.
Workflow templates are the foundation of Process Street. Each template defines a repeatable process as a series of steps with task descriptions, assignments, due dates, data collection fields, and conditional logic. Templates can be created from scratch or customized from the pre-built library, which includes hundreds of templates for common business processes.
When a workflow runs, it creates an instance (called a 'workflow run') that tracks progress through each step. Multiple runs can be active simultaneously — for example, 10 new hire onboarding workflows running in parallel, each at different stages.
Template library and community templates
The template library includes pre-built workflows for employee onboarding, offboarding, IT setup, client onboarding, compliance checklists, and dozens of other processes. Community-contributed templates expand the library further. Each template can be duplicated and customized without affecting the original.
Task assignment and due date automation
Each workflow step can be assigned to a specific user or role with relative due dates (e.g., '2 days after workflow start' or '1 day after previous step completion'). Assignments and due dates update dynamically when workflow runs are created.
Process Street conditional logic and workflow branching
The conditional logic engine allows workflow steps to show, hide, or modify based on input values from data collection fields or previous step outcomes.
The conditional logic engine allows workflow steps to show, hide, or modify based on input values from data collection fields or previous step outcomes. Basic conditional logic is available on the Startup plan, while advanced logic with multiple conditions and nested rules is a Pro plan feature.
For onboarding, conditional logic enables a single workflow template to handle different scenarios — engineering hires see different tasks than sales hires, remote employees get equipment shipping steps while office employees get desk assignment steps, and visa-holding employees trigger additional documentation steps.
Basic vs advanced conditional logic
Startup plan conditional logic supports single-condition rules — if role equals 'engineer,' show step X. Pro plan logic supports multiple conditions combined with AND/OR operators, nested rules, and more complex branching. The decision between plans often comes down to whether your workflows need single or multi-condition branching.
Dynamic task content based on conditions
Conditional logic can modify not just which steps appear, but the content within steps — task descriptions, links, and instructions can change dynamically based on input data. This means a single step can serve multiple scenarios with context-appropriate guidance.
Process Street approval workflows and sign-off management
Approval workflows (Pro plan) allow designated steps to require sign-off from specified approvers before the workflow progresses.
Approval workflows (Pro plan) allow designated steps to require sign-off from specified approvers before the workflow progresses. Approvals can be sequential (one approver after another) or parallel (multiple approvers simultaneously). Rejected approvals trigger notification workflows and can loop back to previous steps for revision.
For onboarding, approvals are useful for equipment purchase authorization, security access provisioning, manager confirmation of new hire setup, and compliance sign-offs. The approval system provides an audit trail of who approved what and when.
Sequential and parallel approval paths
Sequential approvals route through a chain of approvers in order — for example, hiring manager first, then department head, then finance. Parallel approvals send requests to all approvers simultaneously and proceed when all have signed off. The choice depends on your organizational approval structure.
Approval audit trail and documentation
Every approval action is logged with the approver's identity, timestamp, and any comments. The audit trail is accessible from the workflow run history and can be exported for compliance or record-keeping purposes.
Process Street data collection forms and structured input fields
Workflow steps can include data collection fields that capture structured information from users as they complete tasks.
Workflow steps can include data collection fields that capture structured information from users as they complete tasks. Field types include short text, long text, email, URL, date, dropdown, file upload, and more. The collected data is stored with the workflow run and can be used in conditional logic, included in downstream task descriptions, and exported.
For onboarding, data collection fields capture employee information, equipment preferences, emergency contacts, tax withholding elections, and other inputs that feed into subsequent steps or external systems via integrations.
Field types and validation
Process Street supports various field types with optional validation rules — required fields, email format validation, date ranges, and dropdown selections. Validation ensures data quality within the workflow, reducing the manual cleanup that happens when unstructured inputs are collected.
Data export and integration
Collected data can be exported as CSV, pushed to external systems via API or Zapier integrations, and referenced in conditional logic within the same workflow. This data portability means Process Street can serve as a data collection layer that feeds into your HRIS, payroll, or other systems of record.
Process Street integrations, API, and automation connections
Process Street connects to over 1,000 applications through Zapier, native integrations, and a REST API.
Process Street connects to over 1,000 applications through Zapier, native integrations, and a REST API. Native integrations include Slack (notifications and task completion), Microsoft Teams, Google Workspace, and popular CRM and project management tools. The API supports workflow creation, data retrieval, and status updates programmatically.
For onboarding use cases, integrations enable automated workflow triggering from ATS platforms, data syncing to HRIS systems, Slack notifications to managers and stakeholders, and task creation in project management tools for IT provisioning.
Zapier and native integration ecosystem
Zapier connects Process Street to over 1,000 apps for automated triggers and actions. Native integrations with Slack and Microsoft Teams provide deeper functionality including in-channel task completion and notification management. The integration breadth exceeds what most dedicated onboarding tools offer.
REST API for custom automation
The API supports creating workflow runs, updating task status, retrieving collected data, and managing templates programmatically. Custom integrations can automate the entire onboarding trigger-to-completion pipeline without manual intervention.
Process Street reporting and workflow analytics
Reporting capabilities track workflow run status, completion rates, average time-to-completion, overdue tasks, and bottleneck identification across all workflows.
Reporting capabilities track workflow run status, completion rates, average time-to-completion, overdue tasks, and bottleneck identification across all workflows. The Pro plan includes advanced reporting with custom dashboards and deeper filtering.
For onboarding, reports show which workflows are on track, which are delayed, and where bottlenecks consistently occur. This data helps HR teams identify process improvement opportunities and measure onboarding cycle time.
Workflow run status and completion tracking
The dashboard displays all active workflow runs with real-time status — percent complete, overdue tasks, current step, and assignee. For onboarding, this provides a single view of every in-progress onboarding across the organization.
Bottleneck and cycle time analysis
Reporting identifies which workflow steps consistently cause delays. If the IT provisioning step takes 5 days on average while all other steps take 1 day, the bottleneck is immediately visible. This data drives process improvement conversations.