Overview
The Project Export action takes any Taskade project and renders it as a Markdown file or a plain-text file. Use it to back up projects, hand them off to clients, or feed their content into another system like a language model or a wiki.
TL;DR: One action, two formats (Markdown or plain text). Full project structure preserved: tasks, subtasks, notes, and custom field values. See Automations execution for how to chain this action into a scheduled flow.
Inputs
| Field | Type | Notes |
|---|---|---|
| Project ID | String | The project to export |
| Format | markdown / text |
Markdown preserves headings and checkboxes |
| Include completed | Boolean | Defaults to true |
| Include comments | Boolean | Appends each task's comments as a block |
Outputs
| Field | Type | Notes |
|---|---|---|
file |
File | The generated file, usable by any downstream action |
content |
String | The full export as a plain string |
word_count |
Number | Convenience count for length-aware flows |
Example: nightly backup to Drive
- Trigger: Schedule โ Every Day at 02:00 UTC.
- Action: Project Export for each project in a folder.
- Action: Google Drive โ Upload File to a
backups/<date>/folder.
Example: handoff to an LLM
- Trigger: button on a Genesis app.
- Action: Project Export in Markdown.
- Action: AI Action with a prompt that uses the exported content as context.
- Action: post the AI's summary back into the project as a comment.
Tips
- Markdown exports are safe to paste into GitHub issues, Notion, or Obsidian.
- Plain text is the right choice when downstream tools strip Markdown anyway.
- Large projects may take a few seconds; chain a Delay action if your next step is time-sensitive.