# Feature OP-5111 - Expand Webhooks by User Causing

Project: OpenProject
Status: rejected
URL: https://community.openproject.org/work_packages/OP-5111

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

Currently the web-hooks does a great job delivering payload information back.  In fact, it has made it very easy to deliver and process into external applications like Slack.  In dealing with the web-hooks however, I have noticed there is no easy way to delineate what user caused the web-hook to fire and for what reason.

The current hook will tell me a work package was updated and all the associated information for that hook, but whom made the update which caused the web-hook to trigger and also not what they changed.

Making this information readily available would make the integration time significantly faster utilizing the current web-hooks system, maybe through something like:

```json
{
  "trigger": {
    "user": 1,
    "changed": "comment",
  }
}
```

Using slack as an example it currently produces something like the following, but could add details to what was changed and why.

![](/api/v3/attachments/14386/content)

If there is enough demand, we would be willing to expand our implementation into Slack and add commands to push back to OpenProject through v3 API.
