Process Street

Trigger Process Street workflows through conversations, not clicks

When a customer completes onboarding or submits a request, your AI agent kicks off the right Process Street workflow automatically. Checklists launch themselves, data sets update in real time, and your SOPs execute without anyone logging into a dashboard.

Chosen by 800+ global brands across industries

Workflow operations inside every chat

From launching new checklist runs to searching operational data sets, your AI agent triggers Process Street actions the moment a customer conversation calls for them.

Process Street

Use Cases

SOPs that run themselves

See how customer interactions automatically trigger the operational workflows your team already built in Process Street, eliminating the gap between conversation and execution.

Customer Onboarding Starts Automatically

A new customer signs up and says 'I just purchased the Pro plan.' Your AI Agent creates a workflow run from your 'New Customer Onboarding' template in Process Street, populates the customer name and plan details, and sets the due date for 7 days out. Your customer success team finds a ready-to-go checklist waiting for them. No manual trigger needed.

Request Status Lookups Without Back-and-Forth

A customer messages 'What is the status of my refund request?' Your AI Agent searches your Process Street data sets for the matching record, finds the current step in the refund workflow, and tells the customer exactly where things stand. The customer gets an instant update. Your support team handles zero status inquiry tickets.

Compliance Processes Triggered by Customer Actions

A customer submits sensitive documents during a conversation. Your AI Agent launches the appropriate compliance review workflow in Process Street, with a shared link so auditors can track progress. Every step is documented with timestamps. Your compliance team starts their review immediately, with full context from the conversation.

Try
Process Street

Process Street

FAQs

Frequently Asked Questions

How does the AI agent know which Process Street workflow template to launch?

The agent first retrieves your full list of workflow templates via the List Workflows endpoint. Based on the customer's request context, such as 'I need to start onboarding' or 'I want to submit a refund', it matches to the appropriate template by name or ID and creates the run. You can also configure specific trigger rules in your agent's gambit settings.

Can the agent pre-fill form fields when creating a workflow run?

The agent creates workflow runs with a custom name and due date via the API. For deeper field pre-population, the agent can set the run name to include customer details collected during the conversation, giving your team immediate context when they open the checklist.

What happens if the agent creates a workflow run by mistake?

The agent can restore accidentally deleted runs using Process Street's undelete endpoint, recovering the full checklist and its progress. For runs created in error that have not been deleted, your team can manage them directly in Process Street as with any other run.

Does Tars need admin-level access to my Process Street account?

No. Tars uses your Process Street API key, which inherits the permissions of the account that generated it. You can create a dedicated API key with only the access level needed for workflow runs and data set searches.

Does Tars store my Process Street workflow data or records?

No. Tars calls the Process Street API in real time during conversations. Workflow templates, run statuses, and data set records are fetched live and used only to generate the response. No copies of your operational data are stored on Tars servers.

Can the agent search Process Street data sets to look up records?

Yes. The agent uses the Find Data Set Rows endpoint to search within any data set by query criteria. This is useful for looking up customer records, application statuses, or any structured data your team tracks in Process Street data sets.

How is this different from Process Street's native Zapier integration?

Zapier triggers workflows based on events in other apps. Tars triggers workflows based on live customer conversations. Your AI agent understands customer intent, asks clarifying questions, collects required information, and then launches the right workflow. It is interactive and conversational, not event-driven.

Can the agent handle multiple workflow runs for the same customer?

Yes. The agent can create multiple workflow runs from different templates within a single conversation. For example, a customer starting onboarding might trigger both a 'Welcome Checklist' and a 'Technical Setup' workflow, each tracked independently in Process Street.

How to add Tools to your AI Agent

Supercharge your AI Agent with Tool Integrations

Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security

We’ll never let you lose sleep over privacy and security concerns

At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.

GDPR
ISO
SOC 2
HIPAA

Still scrolling? We both know you're interested.

Let's chat about AI Agents the old-fashioned way. Get a demo tailored to your requirements.

Schedule a Demo