# Entity extraction problem due to Slack adding link **URL:** \ **Category:** Rasa Open Source\ **Created:** [December 18, 2018, 8:04pm UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691 "2018-12-18T20:04:09Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![lauraperge](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/lauraperge/32/1073_2.png) [@lauraperge](https://forum.rasa.com/u/lauraperge)\ **Post date:** [December 18, 2018, 8:04pm UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691/1 "2018-12-18T20:04:09Z")
**Rasa Core version** :0.12.3 **Python version** : 3.6 **Operating system** Windows, 64 **Issue** : Cannot extract entity from messages coming from Slack, because Slack recognizes entity as link/email address Hey, So I’m trying to connect my bot to Slack, which works fine, but I have an **email address entity** , which is nicely recognized if I test the bot locally but not with Slack. The reason is that the email address comes from Slack as: [mailto:example@example.com|example@example.com](mailto:example@example.com%7Cexample@example.com) I found something about turning off unfurl or parsing, but I’m not sure how to do this with RASA. Potentially my thoughts of fixing this could be: - Manipulate the strings coming from Slack - but at which point can I so that? - Pass some arguments to the app to disable the above link -but where can I do that again? Thanks! ---
**Author:** ![huberrom](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/huberrom/32/1209_2.png) [@huberrom](https://forum.rasa.com/u/huberrom)\ **Post date:** [December 19, 2018, 8:57am UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691/2 "2018-12-19T08:57:41Z")
For your first option (Manipulate the strings coming from Slack - but at which point can I so that?) you can do it at two points : - A custom component in the pipeline, but I’ll manipulate all the strings, not only the one from Slack (maybe if you have the information of where the message comes from you can change that) ([Custom Components](https://rasa.com/docs/nlu/customcomponents/)) - Or create a custom channel that will treat messages coming from slack and modify the message before it goes in the pipeline ([Chat & Voice platforms](https://rasa.com/docs/core/connectors/#creating-a-new-channel)) I don’t know for the second option, I had the same problem but didn’t manage to find a solution. ---
**Author:** ![zain](https://avatars.discourse-cdn.com/v4/letter/z/6a8cbe/32.png) [@zain](https://forum.rasa.com/u/zain)\ **Post date:** [August 2, 2019, 12:38pm UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691/3 "2019-08-02T12:38:39Z")
@lauraperge did you find a solution for this? I am facing a similar issue ---
**Author:** ![zain](https://avatars.discourse-cdn.com/v4/letter/z/6a8cbe/32.png) [@zain](https://forum.rasa.com/u/zain)\ **Post date:** [August 4, 2019, 12:05pm UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691/4 "2019-08-04T12:05:52Z")
@akelad can you help with this issue? ---
**Author:** ![akelad](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/akelad/32/69_2.png) [@akelad](https://forum.rasa.com/u/akelad)\ **Post date:** [August 16, 2019, 9:54am UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691/5 "2019-08-16T09:54:26Z")
@erohmensing any ideas about this? ---
**Author:** ![erohmensing](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/erohmensing/32/1789_2.png) [@erohmensing](https://forum.rasa.com/u/erohmensing)\ **Post date:** [August 20, 2019, 11:59am UTC](https://forum.rasa.com/t/entity-extraction-problem-due-to-slack-adding-link/3691/6 "2019-08-20T11:59:52Z")
I think this would be a great PR for someone to contribute. Seems like we should manipulate the strings coming from slack in the input channel. Looks like there is already some sanitisation that happens with respect to removing the format for user tags here: [rasa/slack.py at master · RasaHQ/rasa · GitHub](https://github.com/RasaHQ/rasa/blob/master/rasa/core/channels/slack.py#L182) @zain @huberrom @lauraperge would any of you be interested in working on this problem? Would probably be as simple as adding another regex to that sanitizing that checks for the `mailto:` format and converts it back into regular email.