WFTriggers option outputs in the XML the descriptions of all the workflow-execution triggers associated with the object (see http://forum.teradp.com/topic.asp?TOPIC_ID=701). The trigger descriptions are rendered as a 'nav:wfTriggers' element with a 'nav:wfTrigger' sub-element for each trigger. For example, if the 'folder' object with id 5676 has two associated triggers - one on object modifications and one on referencing modifications - executing .../do.ashx?cmd=objsnav&ids=5676&options=wftriggers&max=7 produces:

  <folder nav:objectType="folder" id="obj5676" . . . xmlns:nav="http://www.teradp.com/schemas/GN4/1/ObjNav.xsd">

    <nav:objectTypeAttrs mediaType="None" deadlineGap="0" textElement="" textAttrib="" typeKind="" typeLink="" /> 

    <nav:wfTriggers>

      <nav:wfTrigger mode="Object" name="TestTrigger" priority="10">

        <pars xmlns="">

          <wfSettings>

            <add key="MyPar" value="MyValue" /> 

          </wfSettings>

        </pars>

      </nav:wfTrigger>

      <nav:wfTrigger mode="Referencing" attrName="folderObject.folderRef" name="TestTrigger" priority="5" profile="test"/>

    </nav:wfTriggers>

    . . .

  </folder>

Each 'nav:wfTrigger' element contains attributes specifying when the trigger fires ('mode', 'attrName'), the name of the workflow that is called ('name') and the workflow exection options ('priority' and 'profile'), and finally an optional sub-elements 'pars' (in the default namespace) containing the parameters passed to the workflow.