Overview
The Project Export action takes any Taskade project and renders it as a Markdown file (plain text that keeps simple formatting marks) or a plain-text file. Use it to back up projects, hand them off to clients, or feed their content into another system like an AI model or a wiki. Need spreadsheet-ready rows instead of a document? You can also export any Project View to CSV, covered further down.
TL;DR: One action, two formats (Markdown or plain text). Full project structure preserved: tasks, subtasks, notes, and custom field values. Use it to back up projects, hand them to clients, or feed content into another system. See Automations execution for how to chain this action into a scheduled flow.
Inputs
| Field | Type | Notes |
|---|---|---|
| Project ID | Text | The project to export |
| Format | markdown / text |
Markdown preserves headings and checkboxes |
| Include completed | True or false | Defaults to true |
| Include comments | True or false | Appends each task's comments as a block |
Outputs
| Field | Type | Notes |
|---|---|---|
file |
File | The generated file, usable by any later action |
content |
Text | The whole export as one block of text |
word_count |
Number | A ready-made count when a later step depends on length |
Export a project view as CSV
Need spreadsheet-ready rows instead of a document? Open any project, pick a view, and export it straight to CSV. This is a view-level export, separate from the automation action above, and it is the fastest way to move structured data into Excel, Google Sheets, or a billing tool.
CSV export works from the supported Project Views. Each view decides how the rows are shaped:
| View | What lands in the CSV |
|---|---|
| Table | Every column, one row per task |
| List | Tasks and subtasks with their fields |
| Board | Cards with the column they sit in |
| Calendar | Tasks with their start and due dates |
| Mind Map | Each node with its parent |
| Org Chart | Each role with who it reports to |
Reach for Markdown or plain text when you want a readable document. Reach for CSV when the next tool expects rows and columns.
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: hand off to an AI model
- Trigger: button on a Taskade 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 the next tool strips Markdown anyway.
- Large projects can take a few seconds. If your next step is time-sensitive, chain a Delay action.