# Zendesk Integration: Add Ticket # and Brand Fields **URL:** \ **Category:** Integrations\ **Created:** [March 21, 2025, 12:42am UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484 "2025-03-21T00:42:37Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 21, 2025, 12:42am UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/1 "2025-03-21T00:42:37Z")
Fibery’s Zendesk integration doesn’t pull in the **Brand** field, and surprisingly, it also doesn’t include **Ticket Numbers**. We use Zendesk to manage support for multiple brands within a single instance, which keeps everything well-organized and isolated by brand. Adding support for these fields would be incredibly useful to: - Easily reference tickets by their actual Zendesk **ticket #** - Filter and organize tickets in Fibery **by brand** Since Zendesk natively supports [multiple brands](https://support.zendesk.com/hc/en-us/articles/4408829476378-Setting-up-multiple-brands), having these fields available in Fibery would make a big difference in keeping workflows complete and structured. ---
**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\ **Post date:** [March 21, 2025, 9:11am UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/2 "2025-03-21T09:11:39Z")
Hello, by **ticket #** you mean ticket’s id from Zendesk? We can easily add it. Meanwhile the `url` field contains real id from zendesk so it can be extracted from there into some formula field ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 21, 2025, 12:24pm UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/3 "2025-03-21T12:24:22Z")
Nice! How quickly could it be added? I’m wondering if we should hold off on creating the formula field that extracts the ticket number from the `url`, if this field will be available soon. What’s your take on the **brand** field? I’ve found a potential workaround, but it would require setting up an automation in Zendesk to apply a tag we could then use in Fibery. Ideally, I’d like to avoid relying on external automations where possible. ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 21, 2025, 3:24pm UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/4 "2025-03-21T15:24:14Z")
Another issue is when attaching a ticket to another database — it defaults to displaying by the name field. This is a problem since names aren’t unique in Zendesk. ![CleanShot 2025-03-21 at 11.11.27](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/ce332ded5bf2a037541c793ddb169e9ac1cb95b9.png) **Example from our setup:** I’m trying to link a ticket that reported an issue to its corresponding bug in our **Bugs** database. As you can see, searching by name isn’t helpful here, since multiple tickets share the same name: ![CleanShot 2025-03-21 at 11.14.32](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/95065f58b47265d84557f71d770db7a45250cf33.png) It would be helpful if we could choose which field is displayed in the relation view — like the ticket number or any other field that makes it easier to distinguish between records. ---
**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\ **Post date:** [March 24, 2025, 12:54pm UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/5 "2025-03-24T12:54:23Z")
Already added. You might need to press Sync and then explicitly enable it in “Edit Fields to Sync” ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1c33709eefabca0e7ebd87c399fe43b17686bc1d.png) Will add brands soon as well ---
**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\ **Post date:** [March 24, 2025, 1:16pm UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/6 "2025-03-24T13:16:37Z")
As for “searching by name” problem: At the moment “subject” is used as name. I have some doubts whether it’s a good idea to put id to the name, but I can definitely expose additional “subject” field so later you can just use formula for name field and configure it like `[subject] + [zendesk_id]` ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 24, 2025, 1:36pm UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/7 "2025-03-24T13:36:51Z")
Amazing! 😍 The ticket numbers are now being synced. The solution for the name will definitely do the trick if we can do `[subject]` + `[zendesk_id]`. Any thoughts on also syncing the `brand`? Thank you so much! 🙏 ---
**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\ **Post date:** [March 24, 2025, 4:00pm UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/8 "2025-03-24T16:00:41Z")
@Edan brands are now available as well To sync them you’ll have to go to “Configure” and enable brands there ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/04fa1d0fdbbe59a78939bf5154c7501e78c3f74f.png) Also added Subject field to tickets. Please let me know in case of any problems ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 26, 2025, 12:50am UTC](https://community.fibery.io/t/zendesk-integration-add-ticket-and-brand-fields/8484/9 "2025-03-26T00:50:34Z")
Amazing—thank you so much! Got it working nicely using a formula on the Name field. Way easier to work with tickets now.