getWorkflowDefinition is now live in the Process Street Public API and MCP. It returns a workflow’s complete definition as a single JSON tree, so API integrations and MCP clients can see everything about a workflow before making changes.

What it does

Instead of calling dozens of individual endpoints to piece together a workflow’s structure, getWorkflowDefinition returns the full picture in one request. For a 10-task workflow, that’s one call instead of roughly 60.

The response has two parts:

• Workflow: settings, permissions, webhooks, incoming webhooks, and schedules. Changes to these take effect immediately.
• Revision: a selected revision’s settings, run due date rule, variables, logic rules, and tasks, including each task’s configuration, assignment rules, permission rules, due date rules, and widgets. Edits to revision items go into a draft and take effect when you publish it.

Why it matters for MCP

If you use Process Street through an MCP client (such as Claude), the client now reads the entire workflow before it changes anything. That means more accurate edits, fewer round trips, and plenty of room within the rate limits.

Every item’s properties object is shaped exactly like the matching update tool expects (updateWorkflowRevisionTask, updateWorkflowRevisionTaskWidget, and so on). The client reads a value, changes the field it needs, and sends the object back with no guesswork.

The response also includes an exclusions list that names what the tree leaves out (for example, automations other than AI and Code tasks), so a missing item is never mistaken for one that does not exist. Code task inputs that contain secrets appear as <masked>, and sending that value back preserves the stored secret without exposing it in the conversation.

How to try it

1. Open an MCP client connected to Process Street (or any tool that calls the Public API).
2. Ask something like: “Read the draft of our Client Onboarding workflow and add an approval step after Kickoff call.”
3. The client calls getWorkflowDefinition, sees the full workflow, and makes targeted edits through the existing update tools.

If you don’t see the tool in your MCP client, reconnect the Process Street connector.

Good to know

• getWorkflowDefinition is read-only. Edits still go through the individual update tools, one item at a time.
• The same access rules apply: task configuration and permissions require edit access to the workflow, and webhooks require an Administrator.
• Each person can make 20 requests per minute, and each organization can make 60.
• A workflow too large for one response returns an error rather than a partial tree.

Full endpoint documentation is available at developer.process.st under Workflow Revisions. For more on using Process Street through MCP, see Using Process Street’s MCP Server.