# 🚀 Update: Branch Name Now Included in Webhook Notifications

**URL:** <https://community.transifex.com/t/update-branch-name-now-included-in-webhook-notifications/5012>\
**Category:** What's new?\
**Tags:** integrations, webhooks, git-branches\
**Created:** [November 18, 2025, 5:48am UTC](https://community.transifex.com/t/update-branch-name-now-included-in-webhook-notifications/5012 "2025-11-18T05:48:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sandy\_DLR](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/sandy_dlr/32/2498_2.png) [@Sandy\_DLR](https://community.transifex.com/u/Sandy_DLR)\
**Post date:** [November 18, 2025, 5:48am UTC](https://community.transifex.com/t/update-branch-name-now-included-in-webhook-notifications/5012/1 "2025-11-18T05:48:41Z")

</div>

Hi everyone,

We’ve just released a small but very useful improvement for teams working with multibranch setups. **Webhook notifications for branched resources will now include the branch name in the payload.** This feature is available in the following notifications:

- translation\_completed

- review\_completed

- proofread\_completed

- translation\_completed\_updated

This makes it much easier for custom integrations and automations to understand exactly where the content is coming from and handle it correctly.

Here’s an example of the updated payload:  
`{`  
`“branch”: “test-multibranch/something”,`  
`“event”: “translation_completed”,`  
`“language”: “es”,`  
`“project”: “cli-demo”,`  
`“resource”: “test-multibranch-something–devicexcstrings”,`  
`“translated”: 100`  
`}`

## Why this is helpful

- **Better routing in custom integrations**  
Your system can now easily detect the branch and send the update to the right environment or workflow.

- **Cleaner CI/CD automations**  
Build or deploy scripts can automatically pull the correct content based on the branch—no guessing.

- **Smoother multibranch repo management**  
Useful for teams using feature branches, release branches, or GitFlow-style setups.

- **More visibility and easier debugging**  
Having the branch in the payload helps when reviewing logs or tracking where updates came from.

- **Safer testing vs. production flows**  
You can automatically treat content differently depending on whether it came from a testing branch or a production branch.

* * *

We hope this makes your branching workflows a little easier and cleaner. To learn more about our Webhook feature, click [here](https://help.transifex.com/en/articles/6216204-webhooks).

If you have feedback or want to see more improvements like this, feel free to share your thoughts!