How hard would it be to add a local script execution to the triggers page?

[kwoot]

Currently the triggers page allows sending of email and sms.
I would love to have the option to trigger the execution of a local script, preferable with the ticket id as an argument (more data is of course always nice ).
How hard would it be to make such a functionality?
If I want to start learning ruby, in what file or files should I look to add that?

Kind regards,
Jeroen Baten

p.s. Hm, seems somebody else also requested something similar:

• ACL and execute bash script function
• Enhance trigger and scheduler to run a given script

[MrGeneration]

Maybe @thorsteneckel can tell when he finds some spare time.

Personally I think that this also comes with great security dangers.
My guess at the moment is that this is the try to workaround the missing webhook support which in my opinion would be the better and (imho) safer way to do it.

See:

Outgoing webhook for new/changed tickets

It would be great if it was possible to trigger an outgoing webhook for new/changed tickets. The existing API is useful, but it lacks the “push” type of notification. I can get a list of notification, but in many cases (in example in integration services like Integromat or Zapier) this will not be the best way to trigger an external workflow. While an external workflow is triggered by a change that happened within Zammad it will be easy to use the existing API to do whatever actions are requir…

[kwoot]

Webhooks would work to, that’s true. But executing a local script on a server that has Zammad installed is only as dangerous as the sysadmin managing that system :-). The exact same for the system the webhook that triggers an action. It always happens on a server, and is, again, as dangerous as the sysadmin managing that system.

The reason I ask is that I have been contacted by a startup. They want to trigger bpm processes defined elsewhere when needed based on the contents of the ticket. Based on the backing of the startup I will press them asap to subscribe to one of the zammad pricing plans.

[POleszkiewicz]

Sorry replied from my phone in a totally wrong context.

[thorsteneckel]

Hey guys. Sorry for my late response. @kwoot - unfortunately is this part of Zammad one of the most advanced and I would’t recommend a novice to tackle this as a first task, might be really frustrating. However, for however want’s to give it a shot you can find how we added SMS support here. The changes you are looking for are the ones in the app/models/ticket.rb file. Quite messy down there…