API webhooks should include merged tasks events
not on the roadmap
Jose Heymans
Merging 2 tasks does not trigger any task webhook in the API. It should trigger the "taskUpdated" and "taskDeleted" webhooks, or a new one "taskMerged"
Log In
Canny AI
Merged in a post:
No webhook for merge tasks
H
Harman Lamba
At this moment there is no event being fired when a task is merged into another task. This would be quite useful to track.
Possibly we could get a delete event being fired followed by an update on the target task.
Joey
not on the roadmap
Hey there! Thanks for sharing your feature request with us. We truly appreciate your input!
As part of our efforts to improve our feedback boards, we're closing this older feature request.
Removing old and inactive posts will increase the communication between the ClickUp team and our users, allowing us to hear more of your great ideas!
If you feel this request is worth revisiting, feel free to create a new post!
Thanks for being a part of our community!
Hazem Noor
I'm currently monitoring changes between ClickUp and my application, and I've encountered an issue with merged tasks.
When a task is merged into another, no events are triggered for either of the tasks.
I anticipated that there would be 'taskUpdated' or 'taskDeleted' events, but none were observed.
Although I can know that the task is merged through the 'get task' API, but this process is cumbersome, specially that I don't know when the task is merged.
So, it would greatly streamline the operations to have a dedicated 'taskMerged' event to address this directly.
C
Cassie Lueilwitz
Hello,
i have some write this you can read this
It sounds like you're looking for an event to be triggered when a task is merged into another task, as well as suggestions for events that could be fired in such cases. As an AI language model, I don't have specific knowledge of your software or application's implementation.
I can offer some general suggestions:
Custom Event Implementation: Consider implementing a custom event system within your application. This would involve adding event listeners and triggers at relevant points in your codebase. You can create custom events, such as "taskMerged" or "taskUpdated," and fire these events when the merging and updating of tasks occur. This way, you have full control over which events are triggered and when.
Delete Event: As you mentioned, triggering a "delete" event when a task is merged can be useful for tracking purposes. This event can indicate that a task has been merged into another task. You can provide relevant details in the event payload, such as the IDs or references to the merged tasks.
Update Event on Target Task: Following the delete event, triggering an "update" event on the target task would provide information about the changes made to the task after the merge. This event can include details about the merged tasks, such as their IDs, titles, or any other relevant information that was updated during the merge process.
i hope you can solve the issue.