Great feedback, and I love that you included your specific use case! Exposing richer project metadata — especially tags — through the GET /folders/{folderId}/projects endpoint would make a meaningful difference for workflows that depend on filtering or organizing projects programmatically.

Right now the API response is admittedly minimal on that front. Tags, custom fields, and other project-level attributes are all things we want to surface more completely in the API. Your use case of filtering or routing by tags is a really common developer need, and it reinforces why this matters.

We're actively evolving the Public API and this request is logged and visible to our team. In the meantime, if you haven't already, Taskade Automations can sometimes bridge gaps with tag-based triggers and conditions. Take a look at https://taskade.com/changelog for the latest API and automation updates.

Thanks for the detailed bug report-style feedback — exactly what we need to prioritize the right fields!

We've prioritized this based on your votes and feedback.

We're planning to include this in an upcoming release. Stay tuned for updates!

Follow our progress: Changelog | Product Updates

Thanks for voting and helping shape Taskade!

Any news on this?

hi there, we've since updated our api for projects https://docs.taskade.com/docs/api-reference/projects/get-project-fields

this could be what you are referring to

thanks for your suggestion on adding more api endpoints for projects - we'll take that into consideration.