Skip to main content
Back to timeline
skyvern.comSource publication:

Skyvern renames Workflows to Agents: API moves to /agents, old workflow_id still works

Synopsis

In its June 2026 update, Skyvern renamed Workflows to Agents across the product, public API, and docs, moving the API under /agents and accepting an agent_id alias while existing workflow_id inputs and /workflows endpoints keep working.

Source-provided article image: Changelog
skyvern.com

Interpretation

Skyvern renamed Workflows to Agents across the product, the public API, and the docs, so the call path is now /agents, for example POST /v1/run/agents. Previously these automation flows were named Workflows throughout the product and API, and callers organized requests around workflow_id and /workflows endpoints. The rename covers the product, the public API, and the docs, and the API accepts agent_id as an alias for workflow_id, echoing back the same wpid_ value.

Existing call patterns are not cut off: workflow_id inputs, /workflows endpoints, SDK methods, and bookmarked doc URLs all keep working. The rename is backwards-compatible rather than requiring callers to migrate to the new naming in one step. The same wpid_ value is echoed across the old and new fields, indicating both entry points refer to the same run identifier.

Perspective

This update is aimed at developers using Skyvern's public API, SDK, and docs, and it describes a naming migration across the product, API, and docs, along with the coexistence of old and new entry points. The changelog gives no follow-up migration timeline and does not say when or whether the old naming will be removed.

The changelog describes the rename as fully backwards-compatible but does not say how long the old naming will remain or what conditions would deprecate the old entry points.