Im looking to see if anyone sees editing clickup tasks from obisidian md usefull. We use clickup at our organization and i find it annoying to add tasks sometimes. There are multiple ways to add them in clickup already but i though to try something with obsidian.
Currently just getting/pushing the changes to clickup. I will be adding a way to set the start date etc. from md, but still working on getting basic functionality working.
Example workflow:

Hey there! It’s great to see other people looking for this kind of integration.
Right now, our team is building a dedicated tool for conducting project management natively in Obsidian. Connectors for ClickUp, Jira, and Notion are on our radar and we’re planning to release them very soon. I’ll be sure to update this thread (or let you know) when the ClickUp integration goes live!
Ahh. Very interesting. any sneak peeks? 
Here is my current workflow. i have thought of having the teams, spaces, folders show up as headings and then just look for the headings during lexing/parsing, but i have liked this more explicit approach of highlighting the text more. Currently have it so you setup which list you are working with it. fetch remote → edit → push.
Some stuff i want to add:
- checkbox to complete tasks → also update remote.
- Way to input timeline for a task. maybe extra fields if i find i need them.
- OAauth. currently just apikey in settings.
- Fix bugs.
Stuff there is:
- Get remote
- Display diff
- Create new tasks
- Modify old tasks
- Delete tasks
- Select list you are working on. no way to create spaces etc.


Incredibly cool tool.
I personally dont enjoy making the tasks etc. in GUI. Simple markdown editing is nice for laying out the “base” project, task, etc. structure. Tab indentation, copy paste, AI good with text, fast to work with.. Then refine in GUI. I checked you have all of the tasks stored in md. Based on that a few questions:
- Is there way to edit the tasks in plain markdown or is that planned feature?
- Do you have thread of showcasing your plugin somewhere? such questions might be better suited there.
Thanks, glad you’re enjoying it!
You can already edit tasks in plain markdown today. Each task is its own .md file under <Project>_tasks/ with YAML frontmatter for the structured fields (status, priority, dates, parent, etc.) and the body is a regular markdown note for the description. Edit the file in any editor — the plugin picks up changes on the next refresh. Bulk-creating tasks by duplicating files or piping AI output into the folder works fine, as long as you keep the frontmatter shape and give each task a unique id.
A few things to know if you go that route:
-
pm-task: true and projectId must be set for the plugin to recognize the file.
-
Tree structure comes from parentId / subtaskIds rather than indentation, so if you’re laying out a hierarchy in one buffer first, you’ll need to translate that into IDs when you split it into files.
-
Dates are YYYY-MM-DD strings, statuses are todo / in-progress / blocked / review / done / cancelled.
A “paste markdown outline → tasks” importer is a fair feature request — the indented-list-to-tree workflow you’re describing is exactly the gap. I’ll add it to the backlog.
No dedicated showcase thread yet; for now the GitHub repo issues/discussions are the best place for questions and feature requests. I will make an announcement on the Forum later.