SPIRITTProcess Street

Process Street
Get the right run started

SPIRITT selects existing Process Street workflows, starts the right runs, and coordinates the surrounding work. Data set lookups and a maintained run register keep each handoff tied to its business context.

SPIRITT Workspace input reading Connect me to Process Street, with the Process Street icon in a compact app tile.

What you can do with Process Street.

  • Start the correct procedure

    Match the customer, site, or request to an existing workflow using your routing rules and Process Street data set records.

  • Connect the surrounding work

    Gather documents, coordinate owners, and track created run IDs across your CRM, file library, and operational register.

  • Close on evidence

    Mark a known run complete when its required evidence is satisfied, and request restoration of accidentally deleted runs.

Get started in three steps.

01

Open a workspace

Create a SPIRITT workspace for the recurring procedures and operational handoffs you want to delegate.

A workspace connected to team conversations
02

Connect Process Street

Connect Process Street with an API key granting access to the workflows, data sets, and runs your mission needs.

SPIRITT Workspace input reading Connect me to Process Street, with the Process Street icon in a compact app tile.
03

Delegate a procedure

Name the template and operating rules. SPIRITT launches runs, coordinates inputs, and tracks the outcome across your tools.

Messages and recurring collaboration workflows

Put your procedures into motion

Questions

Process Street, with SPIRITT.

01What can SPIRITT do directly in Process Street?+
It can list available workflows, create a run from an existing workflow, find data set rows, mark a known workflow run complete, and request restoration of a deleted run. SPIRITT combines those actions with connected tools to handle intake, evidence collection, routing, and operational follow-through.
02What access and inputs does a mission need?+
Connect Process Street using an API key with access to the relevant workflows and data sets. Name the existing template, routing rules, and evidence required for completion. For work on existing runs, provide their IDs or a register containing them so each action targets the correct procedure instance.
03Can SPIRITT change individual tasks or rewrite my workflow template?+
The available Process Street actions operate on whole runs and retrieve data set rows; they do not edit template steps or individual task states. SPIRITT can coordinate an established procedure and maintain an external evidence register. Completing a whole run is distinct from updating its individual tasks.
04How can data sets drive useful decisions?+
SPIRITT can find rows using column-value filters, then evaluate returned supplier status, customer tier, site ownership, or renewal dates against your rules. These lookups support routing and decision briefs. It can send correction workbooks to data owners, but the available actions do not write changes into data sets.
05Can it run onboarding across my CRM, documents, and Process Street?+
Yes. A HubSpot deal can supply the customer context, a Process Street data set can select the procedure, and a created run can anchor the handoff. Google Drive holds evidence while Gmail, Slack, and Google Calendar handle requests and coordination. A durable register retains the run identity throughout.
06Can SPIRITT build a run-launching app and recover lost work?+
Yes. It can build a request desk around existing workflows and retain returned run IDs for duplicate prevention and later completion. For accidentally deleted runs with known IDs, it can attempt restoration and record success or failure. Restoration is a separate action from creating a replacement run.
Buy from builders who use what they sellBuilt usingSPIRITT