Hi,From the workflow, you could invoke Message Center API to trigger emails, example:var ctxDynamicTag = <ctx />ctxDynamicTag.appendChild(<tagName>{tagValue}<tagName/>) //your dynamic content if you want to read within delivery template at run time e.g. personalisation details    var mcLogin = logon...

- By recurring email, using SOAP request, I believe you mean: external system will trigger the SOAP API (recurring) which should trigger email (without referring to any nms:recipient record/list)You can use Message Center API (PushEvent), which dont look up to DB but triggers the email directly; exa...

rtEvent.PushEvent: Element is too generic (of type "ANY") as you mentioned. I think consuming systems might face problem as to what child to be created under the same, though they should simply be constructing required child element structure as string and then append it as child tag while sending i...

Got the solution, thanks.

Thanks David- rtEvent API is quite flexible/standard, it accepts XML structure and XML is as-is accesible within message templates, no issue with rtEvent API- The issue is with "PostEvent" API of the xtk:workflow which accepts i/p parameters only within <variables /> tag.The <variables /> tag proper...

Hi,Is there a way to read "child" tags under the <variables> tag, within JS of a workflow?e.g.<variables>     <product>          <name>XYZ</name>          <quantity>2</quantity>     </product></variables>using vars.XXX, will read properties of <variables> tag only but in case of more complex values ...