Creates an automation from the canonical definition. The automation is created INACTIVE; nothing runs until POST /automations/{id}/activate.

Before building a definition, call GET /automations/options for the accepted trigger types, step types, data keys, enum values, and the ids you may reference (email senders, wrappers, chapters, events, funnels, agents). POST /automations/validate runs every check without writing.

Every problem is reported at once with its JSON path. Referenced ids must belong to your organization; a sender, wrapper, page, event, saved list, or chapter from another organization is refused. Names are unique (case-insensitive) within the scope; a duplicate returns 409 unless skip_duplicate_check=true.