Process Street supports creating and running checklists, SOPs, and workflows, helping teams automate recurring processes and track compliance
Process Street supports creating and running checklists, SOPs, and workflows, helping teams automate recurring processes and track compliance On Nagent, Process Street is exposed as a fully-configurable task management integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Process Street into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Process Street to automate the kinds of tasks task management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Process Street into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Process Street, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PROCESS_STREET_COMPLETE_WORKFLOW_RUNThis tool marks an entire workflow run as completed in Process Street. It first retrieves the current workflow run details, then updates the status to 'Completed' while preserving other fields like name and shared status. This distinguishes it from PROCESS_STREET_COMPLETE_TASK which completes individual tasks within a workflow run.
Input parameters
The ID of the workflow run to complete. This is a unique identifier for the workflow run instance, typically a 22-character alphanumeric string (e.g., 'jBAbMsR7BGBdDOLqDUFBmg').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCESS_STREET_CREATE_WORKFLOW_RUNThis tool creates a new workflow run from a specified workflow template. It is one of the most fundamental operations in Process Street, allowing users to initiate a new instance of a workflow. The tool requires a workflow_template_id and optionally allows setting a custom name, due date, and whether to enable a share link.
Input parameters
Custom name for the workflow run
Whether to enable a share link for the workflow run
Due date for the workflow run in ISO 8601 format
The ID of the workflow template to create a run from. This is a 22-character Base64URL-encoded string that identifies the workflow template (e.g., 'jBAbMsR7BGBdDOLqDUFBmg'). You can obtain this ID by using the List Workflows action or from the Process Street UI.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCESS_STREET_FIND_DATA_SET_ROWSRetrieves records from a Process Street data set with optional filtering by column values. Use this tool to search for specific records within a data set or to paginate through all records. Data sets are tables that store structured data which can be used across workflows.
Input parameters
Page number for pagination (1-indexed). Use this with 'limit' to paginate through large result sets.
Maximum number of records to return per page. Valid range is 1-100.
Search query to filter records by column values. Use the format 'columnName:value' to filter records where the specified column matches the value. Leave empty to retrieve all records.
The unique identifier of the data set to search in. You can find this ID in the Process Street UI when viewing a data set, or via the data sets list endpoint.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCESS_STREET_LIST_WORKFLOWSThis tool retrieves a list of all workflows available in the Process Street account. It is a fundamental action that allows users to view and access all their workflows, which is essential for other operations that require workflow IDs. This action is important because it provides the foundation for other actions that require workflow IDs as input parameters, such as creating workflow runs or managing workflow-specific tasks, thereby enabling better workflow management and automation.
Input parameters
Page number for pagination (1-indexed). Use this with 'limit' to paginate through large result sets.
Maximum number of workflows to return per page. Valid range is 1-100.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PROCESS_STREET_UNDELETE_WORKFLOW_RUNRestores a previously deleted workflow run in Process Street. Uses the POST /workflow-runs/{workflowRunId}/undelete endpoint to recover a workflow run within the valid recovery period (typically up to 30 days). Only workflow runs that have been deleted (not permanently removed) can be restored.
Input parameters
The unique identifier of the workflow run to restore. This is a 22-character Base64URL-encoded string that you can obtain from the workflow run creation response or by listing workflow runs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 87 agents privately built on Nagent that already use Process Street.
Build on Nagent
Connect Process Street to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Process Street, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Process Street is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Process Street is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Process Street steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Process Street event fires, the agent kicks off automatically.
Every Process Street action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Process Street ships with 5 pre-built task management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Process Street together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Process Street-based workflows tailored to your business.