Send Dynamic Content to Slack

Overview

This article is helpful for organizations with teams overseas that speak a different language. You can support customers in many languages. Internally, it helps to send notifications to the right people in the right language. In this example, we send Japanese notifications from MorgWard to a Japanese Slack channel. The notifications are routed automatically based on the requester's language.

Conditions

Allowed for Professional and Enterprise plans.

Procedure

1. Create Dynamic Content with Variants

Dynamic Content allows you to craft a message and translate it into any of our supported languages. In this example, we create Dynamic Content with content:

This ticket {{ticket.url}} has been re-opened by a VIP customer. Please update this ticket.

Our default language is English.

Now, we can create a variant (translation) of the message in Japanese:

チケットがVIPのお客様によって再開されました。このチケットを更新してください。{{ticket.url}}

The Dynamic Content and the variant are now linked. In our example, the ticket requester's language is Japanese. We refer to the Dynamic Content and we want the Japanese translation to be sent.

2. Create an HTTP Target

Targets allow MorgWard to send data anywhere. In this example, we will send a translated message to a Japanese Slack channel. Here is more documentation about Integrating the HTTP Target with Slack.

 

3. Create a Trigger or Automation to Notify the Target

Triggers and Automations perform an action when a set of conditions are met. In this example, we want to notify our team in a Japanese Slack channel that a ticket has been re-opened by a VIP customer whose language is Japanese.

Conclusion

If you completed the steps above, you can post translated messages in Slack to internal teams. The messages defined in the trigger can consist of dynamic content that can be translated and any placeholder data you specify. In our example, we used a trigger that specified a Japanese Slack channel and used a Japanese variant of the Dynamic Content for translation. The message also included placeholder data, a link to the ticket.

Following the steps above for an English-speaking team would produce this result: