Abstract
Sometimes when You configure Your workflow's "Send to Slack message" integration, even if You set a type of attachment as "Text", the message's attachment appears on Slack as a binary file.
Problem
An attachment that contains only text for some reason is attached to a message not as a text file, which can be previewed on Slack, for example, but as a binary one. It can happen in a case when the text contains some non-printable characters, so you can not see them, but Slack treats it not as the text file anymore.
Troubleshooting steps
To check that the attached file has some non-printable characters, open the file in a text editor of your choice and turn the displaying of non-printable characters option on.
Remove the non-printable characters from the text and update the content of the attachment.
It's possible that You could paste some of the non-printable characters into the editor while composing the attachment. Please check the content from the clipboard you paste using the same method (displaying non-printable characters in the editor).
It is also possible when you use expressions, and the result of the expression generates these characters. In this case, you need to check the expression itself and where the data for it comes from.
Resolution
Remove all of the non-printable characters from the attachment generator
What's next
If this article did not help, please open a support ticket:
