Process Street
Project ManagementDrive checklist-based processes in Process Street. Agents launch workflow runs from templates, complete or reopen tasks as work progresses, update run statuses and due dates, and read Data Sets to keep recurring SOPs moving.
What This Integration Enables
Process Street's core claim is that the checklist is the evidence: if the run is complete, the process happened. That claim collapses in practice because the work happens in other systems and the boxes get flipped later, from memory, if at all. FlowRunner agents close that gap from both ends. They launch workflow runs the moment the triggering event occurs anywhere in the stack, and they mark tasks complete as the external evidence actually arrives, so the run stops being a retrospective diary and becomes a live record. - Launch workflow runs automatically when records are created in other systems - Mark tasks complete or reopen them as work progresses in external tools - Track run status and due dates from scheduled flows, with stalled steps escalated - Keep completion honest with [human-in-the-loop](/concepts/human-in-the-loop) certification before a run is closed - Read Data Sets to feed structured reference records into process automation
Without FlowRunner
With FlowRunner
Use Case Scenarios
Onboarding that starts itself and assigns itself
A new-hire intake arrives through [Typeform](/integrations/typeform). The agent calls Create Workflow Run against the onboarding workflow, names the run for the hire and start date, and assigns the IT and people ops owners by email. A [Slack](/integrations/slack) message notifies each assignee with the run link. The checklist exists before anyone thought to create it, which is the only version of onboarding that survives a busy week.
The checklist that watches the other tools
Provisioning happens in the identity system, the payroll setup in the HR platform, the laptop order in the procurement tool. As each completes, the agent uses List Tasks to find the matching step in the hire's run and Update Task to mark it Completed. When the setup fails or stalls, the step stays open and honest. The run becomes the one screen that tells the truth about all the systems at once.
The operations review that reads from live runs
Every Monday, the agent runs List Workflow Runs across active processes, pulls each run's progress and due date with Get Workflow Run, and writes the picture to [Google Sheets](/integrations/google-sheets): runs on track, runs stalled, steps overdue and by how long. Overdue runs get their owners flagged in the ops channel. The weekly review starts with the state of every SOP in the company, and nobody compiled it.
Human-in-Loop Highlight
Update Workflow Run with the status set to complete is a certification, not a formality. In the audits, client reviews, and compliance checks where Process Street runs get cited, a completed run is the organization's written assertion that every step of the SOP was followed. An agent that closes runs because the checkable signals look done will eventually certify a process where the uncheckable steps, the conversation that was supposed to happen, the judgment call that was supposed to be made, did not. So FlowRunner agents flip individual tasks as evidence arrives, but the run itself closes only after a person verifies the steps no system can see. The record updates at machine speed. The attestation stays human.
Agent Capabilities
9 actionsWorkflows
2- List Workflows Lists the organization's workflows, the reusable process definitions runs are launched from, with cursor pagination via Limit and Cursor and a nextPageToken for subsequent pages.
- Get Workflow Retrieves a single workflow by ID with its name, status, folder, and metadata. The inspection step before launching a run from it.
Workflow Runs
4- List Workflow Runs Lists workflow runs, the live instances launched from a workflow, filterable by source workflow and status, with cursor pagination. The read behind every process-status sweep.
- Get Workflow Run Retrieves a single workflow run by ID, including name, status, due date, assignees, and progress. Used to check where a running process actually stands.
- Create Workflow Run Launches a new workflow run from an existing workflow, with a name for the run and optional assignees by email. The step that turns a triggering event into a live, owned process instance.
- Update Workflow Run Updates a run's status, for example to complete or archive it, or sets its due date. Only provided fields change. The operation this page's human gate exists for.
Tasks
2- List Tasks Lists the tasks within a specific workflow run, each with name, status, assignees, and due date. Used to inspect progress or locate the step an external event corresponds to.
- Update Task Updates a task within a run, most commonly marking it Completed or reopening it by changing status. The write that keeps the checklist synchronized with work done elsewhere.
Data Sets
1- List Data Sets Lists the organization's Data Sets, structured tables of records referenced from workflows, returning each set's ID and name for selection or lookup.
Frequently Asked Questions
What can FlowRunner do with Process Street?
FlowRunner agents can run List Workflows, Get Workflow, and List Workflow Runs in Process Street, plus 6 more actions.
Does connecting Process Street to FlowRunner require OAuth?
No. Process Street connects to FlowRunner with an API key, no OAuth flow required.
Can Process Street trigger a FlowRunner workflow automatically?
Process Street doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Process Street
$100 in credits. No card required. Connect in minutes.