Skip to content

MngGetWorkflowActionsByTrigger

Returns action definitions allowed for a selected workflow trigger.

Access

Manager sessions: SESSION_MANAGER, SESSION_ADMIN, SESSION_DEALER, SESSION_CRM_MANAGER, SESSION_CRM_ADMIN.

Request Parameters

Name Type Required Description
trigger string Yes Trigger code, for example deposit.created

Request

{
  "command": "MngGetWorkflowActionsByTrigger",
  "extID": "1",
  "data": {
    "trigger": "deposit.created"
  }
}

Response Data

{
  "rows": [
    {
      "code": "kyc.require_step",
      "scope": 0,
      "side_effect_level": 2,
      "supported_payload_types": [1, 3, 5],
      "requires_account": 0,
      "requires_customer": 1,
      "requires_kyc": 1,
      "requires_lead": 0,
      "required_params": ["step_code", "level"],
      "optional_params": ["reason"],
      "recommended_conditions": ["amount_usd", "customer.kyc_current_level"]
    }
  ]
}

recommended_conditions is a UI hint. Backend validation does not require these fields.

bonus.grant

The deposit.created trigger exposes the restricted bonus.grant action. It creates a new OP_BONUS_IN operation through the platform finance core after all rule conditions have matched.

Parameters:

Name Type Required Description
mode string Yes fixed or percent
value number Yes Fixed bonus in account currency, or percentage of the source balance-in amount
max_amount number No Positive cap in account currency, primarily for percentage rules
comment string No Finance operation comment, maximum 256 characters

Percentage example:

{
  "type": "bonus.grant",
  "params": {
    "mode": "percent",
    "value": 20,
    "max_amount": 500,
    "comment": "20% deposit campaign"
  }
}

Fixed example:

{
  "type": "bonus.grant",
  "params": {
    "mode": "fixed",
    "value": 100
  }
}

The generated bonus operation has reason TR_REASON_BONUS_GRANT, references the source balance order through parent_order, and uses a deterministic identifier based on the workflow rule and balance order. Reprocessing the same source event for the same rule therefore does not enqueue a second bonus. TR_REASON_BONUS_CONVERSION balance-in records are rejected by this action. A rule may contain no more than one bonus.grant action; separate promotions must use separate rules.