TORM JSON Schemas

Some of the TORM elements are available to be used in scripts. You can build them in a SNIPPET action to send to contacts . Before using an element, verify that the digital channel you're working with supports that element.

You can send these elements directly using the Outbound API Icon of a square with an arrow point from the center through the top right corner..

JSON schemas are available in the Outbound API on the NiCE CXone developer portal for the following TORM rich media elements: 

  • Text/HTML
  • List pickers
  • Quick replies
  • Time pickers
  • Rich links
  • Adaptive cards

JSON Structure

The JSON for each TORM element described on this page must be properly nested in the following payload structure. Replace <rich content JSON> with the TORM JSON.

Required properties: type, payload

{
 "prompts": [{ 
   "mediaSpecificObject": {  
	"dfoMessage": {  
	  "messageContent": {	
		"type": "PLUGIN"
		"payload": {
		  [rich message payload]
		 }
		"fallbackText": "Text sent as fallback if external platform can't accept rich messages."
		"postback": "Value sent to system to identify what action the user takes"
		}	 
	   ]	   
	  } 	  
     }	
    }	
   }  
  } 
 ]
}

For example: 

{
"prompts": [{ 
  "mediaSpecificObject": {  
    "dfoMessage": {   
      "messageContent": {	
        "type": "PLUGIN",	 
        "payload": {	
          "elements": [{	  
          "id": "bf2521f4-5e85-413f-b6ed-815d1c3905f0",
          "type": "TEXT",	   
          "fallbackText": "Text sent as fallback if external platform can't accept rich messages.",	  
          "text": "This is a successfully created outbound message."
          "mimeType": "text/html"     
        }]
        "postback": "postback-value"  
        "fallbackText": "Text sent as fallback if external platform can't accept rich messages." 
        } 	  
      }	
    }	
   }  
  }]	
}