# Trigger Webhook with Body and Authentication Header **URL:** \ **Category:** Developer Forum\ **Created:** [2. August 2024 um 10:01 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712 "2024-08-02T10:01:11Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![wolfgang](https://avatars.discourse-cdn.com/v4/letter/w/54ee81/32.png) [@wolfgang](https://community.awork.com/u/wolfgang)\ **Post date:** [2. August 2024 um 10:01 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/1 "2024-08-02T10:01:11Z")
Hi, is it possible to pass some entity details to the webhook body? I tried to call a webhook when a task is added to a specific tasklist. That works - but how can i pass the task or taskId thats the cause for the trigger? ---
**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/1305_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\ **Post date:** [7. August 2024 um 17:21 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/2 "2024-08-07T17:21:52Z")
Hi @wolfgang, did you take a look at our webhook documentation? It should send the entity that triggered the event in the body. [Webhooks — awork API | Documentation](https://developers.awork.com/webhooks) If it doesn’t, do you have a trace id of the request (from the headers) and an example of what the webhook request looks like that you receive? Thanks ---
**Author:** ![wolfgang](https://avatars.discourse-cdn.com/v4/letter/w/54ee81/32.png) [@wolfgang](https://community.awork.com/u/wolfgang)\ **Post date:** [8. August 2024 um 05:43 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/3 "2024-08-08T05:43:20Z")
Hi @Sebastian yes i did. And the documentation is correct for the other „default“ webhooks. thats the hook i am talking about. ![grafik](https://europe1.discourse-cdn.com/flex013/uploads/awork1/original/1X/ef9b150208d5c8d26f8341b51faa8366afa7b61b.png) body - thats what i wrote in the text input field. 2024-08-08T05:26:45.1947434Z {entityId} headers (some of them) 2024-08-08T05:26:45.2365868Z Content-Type: application/json; charset=utf-8 2024-08-08T05:26:45.2370226Z Max-Forwards: 10 2024-08-08T05:26:45.2378969Z traceparent: 00-00000000000000007c8b6fe27e0cac25-ed5aa8fb5d4941df-01 2024-08-08T05:26:45.2382839Z tracestate: dd=s:1;p:ed5aa8fb5d4941df;t.dm:-1 2024-08-08T05:26:45.2464425Z Content-Length: 10 2024-08-08T05:26:45.2497226Z x-datadog-trace-id: 8974389701033896997 2024-08-08T05:26:45.2500905Z x-datadog-parent-id: 17103168332448219615 2024-08-08T05:26:45.2504093Z x-datadog-sampling-priority: 1 2024-08-08T05:26:45.2515060Z x-datadog-tags: \_dd.p.dm=-1 2024-08-08T05:26:45.2518522Z X-ARR-LOG-ID: 36ce699d-7f34-439b-a275-1e8820f9049d ---
**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/1305_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\ **Post date:** [8. August 2024 um 06:49 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/4 "2024-08-08T06:49:07Z")
Ah, got it. This is about the webhooks in the project automations. I did a quick check there and it seems like the only thing you can send is the body you specify in the UI here, which is sent as a JSON. So currently no way to add additional information or placeholders unfortunately. ---
**Author:** ![julian\_vierless](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/julian_vierless/32/627_2.png) [@julian\_vierless](https://community.awork.com/u/julian_vierless)\ **Post date:** [20. November 2024 um 13:48 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/5 "2024-11-20T13:48:25Z")
Is there any update on this? It would be super useful for creating custom automations that are currently not supported. In our case we need to update the task type (Tätigkeit) of a task that is created by mail. We found this article here: [https://community.awork.com/t/taetigkeiten-mit-automatisierung-zuweisen/252](https://community.awork.com/t/taetigkeiten-mit-automatisierung-zuweisen/252) It is essentially what we need but since the automation is not supported natively, we tried to built our own in [Make.com](http://Make.com) to handle that. Here the challenge is that we only want to update tasks that are created via email and as far as I can see, there is no way currently to identify if a task was created by email in the JSON body. So, this way is also not working for us at this point in time. **What we want is:** Task from mail is created → Task type is set to „X“ ---
**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/1305_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\ **Post date:** [20. November 2024 um 14:00 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/6 "2024-11-20T14:00:59Z")
Hi @julian_vierless, we don’t have any reliable way to identify how a task was created. The webhook event will contain the task details, which also contains the name and description, which are taken over from the email, so this might help you identify how the task was created. If you need this level of customizations, you might consider using [Make.com](http://Make.com) to listen to emails and create the task in awork. This way you can fully control what fields to set and how. ---
**Author:** ![julian\_vierless](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/julian_vierless/32/627_2.png) [@julian\_vierless](https://community.awork.com/u/julian_vierless)\ **Post date:** [20. November 2024 um 15:26 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/7 "2024-11-20T15:26:54Z")
Ok got it, do you think about implementing some kind of automation for „Tätigkeiten“ in the future? Because it makes a lot of sense to be able to also update dynamically. We are also certain that adding some kind of placeholders/shortcodes in the webhook body from within the built in automations in awork would really help to streamline the automation building. While using [Make.com](http://Make.com) is possible it is a lot of manual work to achieve something that could potentially be done super easily from within awork directly. ---
**Author:** ![julian\_vierless](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/julian_vierless/32/627_2.png) [@julian\_vierless](https://community.awork.com/u/julian_vierless)\ **Post date:** [20. November 2024 um 16:42 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/8 "2024-11-20T16:42:38Z")
A possible workaround (which is really inefficient) might be the following: ![Bildschirmfoto 2024-11-20 um 17.39.45](https://europe1.discourse-cdn.com/flex013/uploads/awork1/original/1X/97f154f42aa2c9e3740c2e229648078d9e79f658.png) 1. A task is created 2. ChatGPT checks if the content in the task’s description field looks like it might be an email 3. If yes, we continue and update our task via API ---
**Author:** ![Sebastian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.awork.com/sebastian/32/1305_2.png) [@Sebastian](https://community.awork.com/u/Sebastian)\ **Post date:** [20. November 2024 um 17:21 UTC](https://community.awork.com/t/trigger-webhook-with-body-and-authentication-header/1712/9 "2024-11-20T17:21:54Z")
Thanks for the feedback! We currently don’t have any changes to the webhooks planned but are happy to hear what use cases currently are not covered. We use our webhooks internally a lot to automate workflows and found that we can usually implement them quite easily. We use [n8n](https://n8n.io/) for most of those, which gives us a lot of flexibility. We also have an [awork node](https://www.npmjs.com/package/n8n-nodes-awork) for n8n which covers some basic use cases.