Workflow triggers refuse misplaced conditions, and run type is now writable

POST /api/v2/workflows/:workflow_id/triggers and PATCH /api/v2/workflows/triggers/:id now return 422 when a trigger field such as funnel_id or page_id arrives anywhere but directly on workflows_trigger, for example inside a settings object. The error names each misplaced field and nothing is saved. Before, the request succeeded and the trigger was created with no condition at all, so a workflow meant for one opt-in page fired for every opt-in in the workspace and could email people who never asked for it.

PATCH /api/v2/workflows/:id also accepts run_type (asynchronous, synchronous or one_time) instead of silently ignoring it, so deciding whether a contact can run through a workflow more than once no longer means opening the app.

Agent examples: scope an opt-in workflow to a single page and trust that it stayed scoped · switch a welcome sequence to one run per contact

Resources: Create Trigger · Update Workflow
Building with an AI agent? Point it at the Workflows skill.