Without knowing anything about SNOW I would assume it would depend on any APIs or other ways to get data into the software. There’s unlikely a native way to do it form Cloverleaf, you’d likely need to write a script to format data in whichever way SNOW will take it to create a ticket. We use SolarWinds here for our ticketing system and I’d just jump to sending an email, it’s likely the easiest way.
They generally do have API’s. I am currently prototyping a JSON feed using oauth2 on Webservices to Halo(BMC). I have email alerts that I am now going to drop using the existing variables into a VRL which get translated into JSON. Functionally working just need to get more of the detail as to exactly what will create the ticket as desired. Should be faster than email since I am currently seeing 48 minute and longer delays in the email. I would bet that SNOW has the documentation for establishing a connection to receive ticket information and generate a ticket.
We have completed integrations with Slack via webhooks, Teams(don’t like the workflow), Pager Duty. We are moving to SNOW we had Fresh Desk. However, we did opt for the emails with that then Freshdesk did the internal flows. SNOW has robust APIs for the management hopefully when we go there. Up to you but we struggle sometimes with repetition and creating more than one ticket when all goes sideways. Managing that is the difficulty.
.
