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?
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
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
Hi @Sebastian
yes i did. And the documentation is correct for the other „default“ webhooks.
thats the hook i am talking about.
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
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.
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
It is essentially what we need but since the automation is not supported natively, we tried to built our own in 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“
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 to listen to emails and create the task in awork. This way you can fully control what fields to set and how.
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 is possible it is a lot of manual work to achieve something that could potentially be done super easily from within awork directly.
A possible workaround (which is really inefficient) might be the following:
- A task is created
- ChatGPT checks if the content in the task’s description field looks like it might be an email
- If yes, we continue and update our task via API
1 „Gefällt mir“
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 for most of those, which gives us a lot of flexibility. We also have an awork node for n8n which covers some basic use cases.