Reference documentation available at https://docs.servicenow.com/bundle/kingston-security-management/page/product/secops-integration-splunk-addon/concept/manual-search-commands.html#security-incident The command needs to be at the beginning of your search, preceded by a pipe character. E.g. | snsecevent node TESTnode type TESTtype resource TESTresource You can see the workflow action in Splunk under Fields -> Workflow actions, which shows the equivalent search using placeholders. Are you able to use the | snowevent or | snowincident commands in the ServiceNow add-on? Reference: https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Commandsandscripts Finally, if you have access, you could try script execution of the TA_ServiceNow_SecOps/bin/sn_sec_event.py per the commands.conf mapping. The relevant parameters are passed into a datamap[] and then to the SNOW REST API NB: sn_sec_event_alert.py maps to the actions specified in the alert_actions.conf file, which aligns with the GUI fields in the Security Operations Integration add-on. Hope that helps.
... View more