Please go to the following website, if you need more information: You can also use other resources which are provided by the Slack REST API. More information about the Slack REST API The output in the OTRS debugger should look like the following:īecause of the received JSON data from Slack, we should also see the message now in our Slack channel Create a new ticket and see if the invoker is triggered: Congratulations! You’re done with the invoker. Don’t forget to set “POST” as request command.Īpply all changes. I’ve added the first part until the “/” to my endpoint address and the second part including the “/” I added to the controller mapping. My Slack token is “T0X829D7E/BBYH0BEE4/nAFuXxXxXxXxXxXxXxXxXxX2”. I’m using a small workaround to make the integration possible. The next part is the configuration of the transport. That’s all for the invoker configuration. Because I want to inform my Slack users every time when a new ticket is created, I’m using the “TicketCreate” event without any event filters: The last part for the invoker is the used event trigger. The following example is tested and working: The most important part is (as always) the XSLT mapping. Attached you’ll find the first part of my config: Configure the SlackConnector on OTRS sideĪt first, we’ve to create the new web service.Īfterward, we need a new invoker. Like in former blog posts, there are several requirements for this HowTo:įollow the instructions and create a new incoming webhook. So let’s start with our “SlackConnector”. Because I’m also evaluating Phantom at the moment and was invited to join their Slack community, I thought this would be a nice use case. During my vacation, I thought about new integration use cases I can show you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |