ceven

Process Street

Triggers checklist runs from external events, monitors SOP completion for compliance, and syncs process data into your central database as tasks finish.

Try Process Street in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Process Street integration

    • Describe the outcome and Ceven picks the right Process Street calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Process Street data, across all 5 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Process Street access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Process Street, when, and on whose behalf.
    • The agent pauses and asks when Process Street is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Process Street.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Process Street action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Process Street, and when to use it.

Create workflow run
Use this to start a new instance of a checklist from a template. Common for onboarding a new hire or starting a project kick off.
Complete workflow run
Mark an entire process instance as finished. Use this to trigger downstream automation once all SOP steps are verified.
Find data set rows
Search for specific records within a data set using form fields. Use this to pull historical process data for a specific client.
List workflows
Pull a list of all available workflow templates. Use this to find the correct template ID before starting a new run.
Undelete workflow run
Restore a previously deleted process run. Use this when a run was accidentally removed during cleanup.
Get run details
Pull the current status and field values of a specific workflow run. Use this to check if a task is pending.
Update task status
Mark a specific task within a run as complete. Use this to sync progress from an external project tool.
Add run comment
Post a note to a specific workflow run. Use this to log AI generated summaries of a process step.
Search runs
Query active or completed runs by name or user. Use this to find all open onboarding checklists for a region.
Assign run owner
Change the person responsible for a workflow run. Use this to route a process to a different manager.
Get template info
Pull the structure and required fields of a workflow template. Use this to validate data before creating a run.
List run tasks
Pull all tasks associated with a specific run. Use this to audit which steps are still outstanding.
Complete a workflow run
This tool marks an entire workflow run as completed in process street. it updates the workflow run's status to 'completed', distinguishing it from process street complete task which completes individual tasks.

13 actions · scroll to see them all

Frequently asked questions

Ceven operates using the permissions granted to the API key or OAuth token provided during connection. If the connecting user has admin access to all workflows, the AI agent can see and manage those runs. If the user is restricted to specific folders or templates, Ceven will only be able to interact with those specific assets. We recommend using a dedicated service account with the minimum necessary permissions to maintain a clean audit trail. This ensures that the agent cannot accidentally modify templates that should remain locked for compliance reasons.
Yes. You can build a workflow where a Google Calendar or Outlook event triggers the Create Workflow Run action. For example, when a discovery call is scheduled, Ceven can automatically launch a Pre Call Research checklist in Process Street and assign it to the account executive. The agent can even pull the guest list from the calendar invite and populate the initial form fields in the checklist so the user does not have to enter the data manually.
If a run is deleted, the connection in Ceven remains, but any attempts to update that specific run will return a not found error. However, Ceven can use the Undelete Workflow Run action to recover it if the deletion happened recently. We suggest setting up a monitoring workflow that alerts your team if a critical compliance run is deleted, allowing the agent to either restore it immediately or log the event in your security audit trail for review.
Yes. Process Street enforces rate limits on their API to ensure platform stability. If your workflow triggers thousands of runs in a very short window, you may encounter 429 Too Many Requests errors. Ceven handles this by implementing an exponential backoff strategy, meaning the agent will automatically pause and retry the request after a short delay. For extremely high volume accounts, we recommend batching updates or spacing out the triggers to avoid hitting these limits during peak business hours.
Ceven can read any data stored in the form fields of a workflow run. This includes text inputs, dropdown selections, and checkboxes. By using the Get Run Details action, the agent pulls the current state of the process. This allows the AI to make decisions based on the data. For instance, if a checkbox for High Risk is marked in Process Street, Ceven can automatically trigger an additional approval run for the legal team.
Ceven interacts with the resulting state of the workflow run. While the conditional logic lives inside Process Street to determine which tasks appear to the human user, Ceven sees the final set of completed tasks and field values. You can use Ceven to act as an external logic engine that triggers different Process Street templates based on data from other apps, effectively extending the native conditional logic of the platform across your entire software stack.
Ceven focuses on the execution and management of workflow runs rather than the design of the templates themselves. While the agent can list workflows and start new runs, it cannot currently build the structural layout of a new template from scratch. You should design your SOPs and checklists within the Process Street editor first. Once the template is published, Ceven can handle the automation of starting, tracking, and closing those runs based on your business rules.
Ceven uses the Find Data Set Rows action to treat Process Street data sets like a searchable database. The agent can query these rows to find specific information, such as a client ID or a project code, and then use that information to trigger a new run or update an existing one. This is particularly useful for recurring processes where you need to pull the most recent data from a previous run to populate the fields of a new instance.

Alternatives to Process Street

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Pipefy logoPipefyMonday logoMondayClickUp logoClickUpTrello logoTrello

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Process Street and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free