Move a workflow into a folder
workflow:writeFiles the workflow under one folder, or un-files it. A workflow lives in at most one folder; folderId: null (or an omitted field) means uncategorized. The target folder must belong to the SAME workspace — a folder id from another tenant is refused with 400 Folder not found, which is also what you get for a folder that does not exist at all.
Like the tags route this is a dedicated column write: it does not touch the definition, mint a version or bump definitionRev. Folders themselves are created and listed through /api/folders.
Authorization
bearerAuth An API token: Authorization: Bearer grt_…. Mint one in the app under Settings → Workspace → API tokens; the raw value is shown once. Scopes confine the token — see x-permission on each operation.
In: header
Path Parameters
Workflow id.
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X PUT "https://example.com/api/workflows/497f6eca-6276-4993-bfeb-53cbbbba6f08/folder" \ -H "Content-Type: application/json" \ -d '{ "folderId": "3f1b0f0a-2c4e-4b21-9b0e-6d5a2f8c1234" }'{ "data": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "folderId": "5b6379a4-2a6c-4085-b184-45838a3b8e7e" }}