/mcp<WorkflowAction> <uri>/finesse/api/WorkflowAction/{id}</uri> <name></name> <type></type> <handledBy></handledBy> <params> <Param> <name><name> <value></value> </Param> <Param> <name></name> <value></value> </Param> </params> <actionVariables> <ActionVariable> <name></name> <type></type> </ActionVariable> </actionVariables> </WorkflowAction> There are two types of workflow actions: BROWSER_POP and HTTP_REQUEST. The BROWSER_POP type is structured as follows: <WorkflowAction> <uri>/finesse/api/WorkflowAction/{id}</uri> <name>DuckDuckGo</name> <type>BROWSER_POP</type> <handledBy>FINESSE_DESKTOP</handledBy> <params> <Param> <name>path<name> <value>http://www.example.com?q=${callVariable1}</value> </Param> <Param> <name>windowName</name> <value>theWindow</value> </Param> </params> <actionVariables> <ActionVariable> <name>callVariable1</name> <type>SYSTEM</type> </ActionVariable> </actionVariables> </WorkflowAction> The HTTP_REQUEST type is structured as follows: <WorkflowAction> <name>Test with Content Type</name> <type>HTTP_REQUEST</type> <handledBy>FINESSE_DESKTOP</handledBy> <Param> <name>path</name> <value>http://www.example.com?q=${callVariable1}</value> </Param> <Param> <name>method</name> <value>PUT</value> </Param> <Param> Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 304 Cisco Finesse Configuration APIs WorkflowAction