# Add Tags support to Discourse integration

**URL:** <https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820>\
**Category:** Integrations\
**Created:** [July 19, 2021, 6:12pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820 "2021-07-19T18:12:51Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [July 19, 2021, 6:12pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/1 "2021-07-19T18:12:51Z")

</div>

I find the Discourse integration with Fibery to be very useful. However it appears to lack support of Tags, which for many forums - and for feedback processes in particular - is highly valuable. Without this support, you are limited to use of Categories, which are less flexible, and you also have only a limited amount of “nesting” you can do.

So I would like to request the addition of Tags support. I’m not sure if it should be a Type of its own like Category, but probably. Alternatively, perhaps a multi-select.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [August 2, 2021, 6:35pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/2 "2021-08-02T18:35:32Z")

</div>

Type will work better here for sure.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 2, 2021, 6:48pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/3 "2021-08-02T18:48:05Z")

</div>

I take that to mean you will implement it, at least some time. 😉

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 12, 2021, 9:16pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/4 "2021-08-12T21:16:11Z")

</div>

@mdubakov I would love a bit a bit more clarity around whether you have intention to support this (and ideally to know how difficult/time consuming it is). Your own feedback process seems to connect heavily with use of tags in the forum, so surely it is of value to your own team, at least. And I know Discourse integration is not heavily used yet (I aim to change that though!), but I do hope the value for your team at least contributes notably to implementing this…

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 21, 2021, 9:16pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/5 "2021-08-21T21:16:36Z")

</div>

@mdubakov I know this is almost certainly a low priority, but I was also hoping it would at least be one of either A: something that could be _implemented_ quickly, or B: something that could be _answered_ quickly with a reason why not. 😉 And I hate to do it, but you did promise some improvements in response time…

> [@repeat Community Re-start](https://community.fibery.io/t/community-re-start/1881):
>
> Fibery Community provided tons of feedback and ideas already, thank you all! But we never paid enough attention to it. Now, this is going to change. We have a dream that in future it will be possible to use Fibery to build a community like this. So we are going to test some approaches and maintain integrity between Fibery and Community manually to see whether it has any value. Here are some additions and rules: four_leaf_clover Each started or soon-to-be-started feature will have its repre…

Maybe @Chr1sG has some thoughts now that he’s on the inside? 😁

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [August 25, 2021, 9:33pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/6 "2021-08-25T21:33:37Z")

</div>

I’ll try and see what I can find out. I’m afraid Michael is ‘out-of-office’ at the moment. Apologies from us both for not replying sooner.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 25, 2021, 10:23pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/7 "2021-08-25T22:23:31Z")

</div>

Thanks! This ongoing thread over on Discourse Meta may be relevant (and the Integromat thread it links to):

> **[Add query for tag assignment changes on topics to API](https://meta.discourse.org/t/add-query-for-tag-assignment-changes-on-topics-to-api/201730)**
>
> As-mentioned here by Integromat: It appears that there could be some improvements to how tag assignments on topics are exposed through the API. Specifically, the ability to query for newly-added tags on topics. My particular use case is to use...

In short, I’m not sure if there is a limitation in the Discourse API for tags, or if they are exposed and it’s just change detection that must be done via Webhooks. If that’s the case, then it should be possible for Fibery to support them since its integrations are mostly “naïve” in the sense that they just pull all data each sync, from what I understand. But obviously if tags aren’t supported in the API at all, then Webhooks would be the only way.

If Webhooks are they way, I imagine that’s something I could do within Fibery already, setting something up to “enrich” the existing Discourse synced data using an action button or automation or something. But it’d be a lot nicer just to have it be part of the integration.

---

<div class="post-metadata">

**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\
**Post date:** [September 9, 2021, 9:19am UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/8 "2021-09-09T09:19:38Z")

</div>

Hi!  
Just checked - we will add those Tags in the next release - next week 🤗

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [September 9, 2021, 3:17pm UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/9 "2021-09-09T15:17:28Z")

</div>

I’m _so_ glad to hear this, thank you for checking! This will make Fibery + Discourse _much_ more powerful and useful.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [September 13, 2021, 7:05am UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/10 "2021-09-13T07:05:59Z")

</div>

Tags support for discourse is released [CHANGELOG: Sep 12 / Slack app, "Entity linked" trigger, Permissions for select Fields](https://community.fibery.io/t/changelog-sep-12-slack-app-entity-linked-trigger-permissions-for-select-fields/1996)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [September 13, 2021, 7:06am UTC](https://community.fibery.io/t/add-tags-support-to-discourse-integration/1820/11 "2021-09-13T07:06:26Z")

</div>


