[API 2.0] Get task content
completed
Roman Wollenburg
Make task's content available via task-api. Gladly optional, and gladly as markdown or html to get full content. Another approach: Additional API-Endpoint to get Task-Content by taskId
Log In
Autopilot
Merged in a post:
Provide task content in the response of fetched tasks
Ali Safari
Unfortunately the endpoint of fetching tasks does not have "content" attribute in the response, it only has "text_content" which is not useful for me, it's causing us need to call each task separately as a single task to get the full "content" which eventually leads us to have a huge amount of requests for importing all tasks of a workspace
Endpoint:
Philipp Berner
completed
GET Task endpoint (https://developer.clickup.com/reference/gettasks) contains now the option include_markdown_description to get the Task Desc as Markdown.
There are improvements on our roadmap on the markdown to internal Quill conversion.
I also updated our Task guide (https://developer.clickup.com/docs/tasks#task-relationships) to elaborate on Task relationships.
Philipp Berner
Our GET Task endpoint (https://developer.clickup.com/reference/gettasks) contains now the option
include_markdown_description
to get the Task Desc as Markdown. Would that satisfy the needs of this request
C
Conor Nash
Philipp Berner This is definitely an improvement. However, it seems that links to other tasks are not included as part of this, leaving parts of the task content absent. Can you confirm?
Jack Nasarzewski
Philipp Bernerr still looking how to get email address to a task .
Philipp Berner
Jack Nasarzewski: We don't have this at this point. I have been in conversation about adding this.
Philipp Berner
Conor Nash: I updated the guide for Tasks (https://developer.clickup.com/docs/tasks) explains how to get task links and dependencies and how to set and remove them.
James Barry
Same thing for Task Comments, markdown or html of comments would be great in webhook payloads or GetComment API
F
Felix Schmidt
As of a few weeks ago, 90% of this feature has been added in an update.
A new field "description_markdown" was added for GET, PUT and POST operations.
I haven't tested a lot of different markdown types, but most of it seems to work.
There is only one HUGE bug: Exporting the "description_markdown" and re-importing the exact SAME string via PUT/POST destroys and scrambles the text in ClickUp. Not for every type of markdown, but a LOT!
Ali Safari
At least can you please provide us the endpoint of getting tasks with their ids? that endpoint is being used on your production, but the public api does not support it, this is the only way for me to fetch all tasks including their content, otherwise I have to send single request per each task in order to importing all tasks of a space
F
Felix Schmidt
To improve the functionality, it would be beneficial to include support for GET, PUT, and POST operations. A similar approach to handling comments can be employed, where you can already retrieve an array of text block elements with attributes like italic: true.
Implementing Markdown and HTML support would be even better since it would save each one of us from having to individually map ClickUp's special notation to markdown/HTML and vice versa.
Fortunately, the current manual import functionality available for documents can handle different file formats. Just copy that to over to the API.
Philipp Berner
Felix Schmidt: Thank you for elaborating and highlighting this.
We're doing some work towards a new API v3 interface. We're aiming to have a unified way to deal with formatted text across the entire API.
Aschkan Fardoose
We need to have task content as markdown. This is crucial for us.
Pierre Becher
Currently tasks assigned to teams are not returned in the API. This is a significant lack and nowhere documented in the API documentation.
B
Brian Shen
considering
Load More
→