Enables a module — such as approval, opinion, credit/decision engines, or messaging — on a phase.We recommend following a two-step activation pattern, always in this order: first configure the corresponding module (approval-config, opinion-config, credit-engine-config, among others), and only then create this phase action. Without the prior configuration, creation returns a 400 error.The action field accepts exactly 11 values: approval, agrisk, opinion, decision-engine, create-document-enable, create-document-auto, credit-engine, messaging, conversation, financial-report, and income-tax. Bureau/AgRisk lookups use the value agrisk.Regarding the blocksMovement field: for opinion and approval, it should always be true, since the card cannot advance until the module is completed; for messaging, it should always be false; for the engines (credit-engine and decision-engine), the default is false, with true reserved for specific exceptions.The conditions field is required and cannot be sent empty — the API returns a 400 error in that case. A safe default value is [{rule:[{field:"card.value",condition:"gte",target:0}]}]. Inside rule[], the key that identifies the evaluated field is field; using path returns a 400 error.Configuration order matters: configuring approval-config or opinion-config along with their rules, without creating the matching phase action, does not produce an API error — but the vote or opinion button simply will not appear to users on that phase. We recommend always creating the phase action right after configuring the module.The create-document-enable and create-document-auto modules work together: enabling only one of them leaves the manual generation button without effect if the corresponding document template and auto-generation configuration are missing.