# Taiga Webhooks: Passing along connected EPIC of USERSTORY/TASK

**URL:** https://community.taiga.io/t/taiga-webhooks-passing-along-connected-epic-of-userstory-task/2524
**Category:** Feature requests
**Created:** [January 24, 2024, 6:59pm UTC](https://community.taiga.io/t/taiga-webhooks-passing-along-connected-epic-of-userstory-task/2524 "2024-01-24T18:59:36Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Komarovo](https://avatars.discourse-cdn.com/v4/letter/k/ce7236/32.png) [@Komarovo](https://community.taiga.io/u/Komarovo)
#### Post date: [January 24, 2024, 6:59pm UTC](https://community.taiga.io/t/taiga-webhooks-passing-along-connected-epic-of-userstory-task/2524/1 "2024-01-24T18:59:36Z")

</div>

I’m using Taiga’s webhooks to update people about activity on a specific taiga project on a different platform.  
When a task or userstory is created or edited I also want to show the according epic. This information is sadly not passed along in the webhook.

Ref. [Taiga: Webhooks](https://docs.taiga.io/webhooks.html), chapters 4.3 and 4.4

---

<div class="post-metadata">

### Author: ![david.barragan](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/david.barragan/32/293_2.png) [@david.barragan](https://community.taiga.io/u/david.barragan)
#### Post date: [January 25, 2024, 12:29pm UTC](https://community.taiga.io/t/taiga-webhooks-passing-along-connected-epic-of-userstory-task/2524/2 "2024-01-25T12:29:32Z")

</div>

Yes, currently the Epic information is not being sent. The only work around I can think of is to make an API call to query that information when receiving a webhook.

---

<div class="post-metadata">

### Author: ![Komarovo](https://avatars.discourse-cdn.com/v4/letter/k/ce7236/32.png) [@Komarovo](https://community.taiga.io/u/Komarovo)
#### Post date: [January 25, 2024, 4:08pm UTC](https://community.taiga.io/t/taiga-webhooks-passing-along-connected-epic-of-userstory-task/2524/3 "2024-01-25T16:08:24Z")

</div>

I was thinking the same. Making an additional API call isn’t the most elegant solution but the only one we have at this point of time.  
I do wonder how easily this could be fixed/added to the current version of Taiga.
