How to connect Process Street to OpenClaw
Connect Process Street to OpenClaw with ClawLink: paste your Process Street key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.

Process Street supports creating and running checklists, SOPs, and workflows, helping teams automate recurring processes and track compliance.. Once connected, OpenClaw can read and act on Process Street from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Process Street access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Process Street setup: install one ClawHub skill, connect Process Street in the browser, and OpenClaw can call real Process Street actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Process Street.
- 1
Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin - 2
Connect Process Street
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Process Street?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Process Street in the ClawLink dashboard — paste your Process Street API key once.
Verify the connection by asking OpenClaw:
Use Process Street to find data set rows and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Process Street is connected in the dashboard, that agent calls the same 13 Process Street tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Process Street MCP for OpenClaw
Looking for a Process Street MCP server for OpenClaw? ClawLink connects Process Street to OpenClaw and exposes 13 Process Street tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Process Street integration works the same way.
What the OpenClaw Process Street integration can do
13 Process Street tools are ready for OpenClaw once the account is connected.
All 13 Process Street tools for OpenClaw
| Tool | What it does |
|---|---|
Find data set rows process_street_find_data_set_rows | Retrieves records from a Process Street data set with optional filtering by column values |
Get task assignment rules process_street_get_task_assignment_rules | Return assignment rules for a task in a selected workflow revision |
Get workflow process_street_get_workflow | Return one Process Street workflow definition by its unique identifier |
Get workflow run process_street_get_workflow_run | Return details for one Process Street workflow run |
List page revisions process_street_list_page_revisions | Lists one page of revisions for a Process Street page |
List workflow revision tasks process_street_list_workflow_revision_tasks | Return one page of tasks defined on a selected workflow revision |
List workflow revisions process_street_list_workflow_revisions | Lists one page of revisions for a Process Street workflow |
List workflow tasks process_street_list_workflow_tasks | Return one page of task templates belonging to a workflow |
List workflows process_street_list_workflows | Lists a page of workflows available in the Process Street account, helping you find workflows |
Search workflow runs process_street_search_workflow_runs | Search the latest 200 workflow runs, most recently updated first |
Complete workflow run process_street_complete_workflow_run | Marks an entire workflow run as completed in Process Street |
Create workflow run process_street_create_workflow_run | Creates a new workflow run from a specified workflow template |
Undelete workflow run process_street_undelete_workflow_run | Restores a previously deleted workflow run in Process Street |
Try it: find the Process Street tool you need
Browse the 14 Process Street tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Process Street to find data set rows and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Process Street working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Process Street API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Process Street account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Process Street. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Process Street actions to the runtime in a format your agent can reliably use. | 13 tools for Process Street are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Process Street to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Process Street in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Process Street key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Process Street skill but can't call the tools
The ClawHub skill teaches OpenClaw about Process Street, but the calls run through the ClawLink plugin and your connected account. Make sure Process Street is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Process Street from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Process Street tools
Process Street tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Process Street call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Process Street returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Process Street has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Process Street integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Process Street: link your Process Street account once in the browser and OpenClaw can call the Process Street API through 13 ready-made tools — no custom code or token handling.
How do I add Process Street to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Process Street skill from ClawHub, then you click Connect in the dashboard to authorize Process Street. OpenClaw calls the tools from the next message — no config files, and the Process Street key you paste is stored server-side instead of in your environment.
How long does it take to connect Process Street to OpenClaw?
About two minutes. Sign in, click Connect next to Process Street in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Process Street up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Process Street working from chat.
OpenClaw installed the Process Street skill but can't call the tools
The ClawHub skill teaches OpenClaw about Process Street, but the calls run through the ClawLink plugin and your connected account. Make sure Process Street is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.