[GH-ISSUE #8330] [FR] Add option to export tables to Excel manually or automatically (via Zapier or similar integration) #3733

Open
opened 2026-03-23 21:32:47 +00:00 by mirror · 2 comments
Owner

Originally created by @KriszDK on GitHub (Nov 6, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8330

Description

Currently, tables created in AppFlowy cannot be exported directly to Excel (.xlsx) format.
For users who use AppFlowy to manage structured data — such as logs, project tracking, or automation input — it would be extremely useful to export tables into Excel files.

Proposed features:
1. Manual export:
• Allow users to manually export any table (or database view) as an .xlsx file.
• The export option could appear in the table’s menu (e.g. “Export → Excel”).
• Each export should preserve column headers, formatting, and data types.
2. Automated export (integration support):
• Allow exporting tables automatically through integrations such as Zapier, Make (Integromat), or AppFlowy API hooks.
• Example use cases:
• Export a table to an Excel file daily.
• Trigger an export whenever a new row is added or updated.
• The exported file could be saved to a user-specified folder or cloud storage (e.g. OneDrive, Google Drive, Dropbox).

Impact

Makes AppFlowy much more compatible with existing workflows that depend on Excel files.
• Allows users to reuse AppFlowy data in automated processes, reports, and analytics tools.
• Reduces manual work for users who periodically need to sync AppFlowy tables with other systems.
• Increases productivity for developers, analysts, and makers who rely on Excel-based automations.
• Enhances integration potential with third-party automation platforms.

Additional Context

often use AppFlowy tables to organize project or workflow data, and I need to periodically process that data in Excel-based automation scripts.
Having both manual export and automatic export via Zapier or similar tools would make AppFlowy an even more powerful productivity platform.

Example scenario:
• I maintain a project status table in AppFlowy.
• Once a day, or when new data is added, the table is automatically exported to Excel and processed by an external automation script.

Originally created by @KriszDK on GitHub (Nov 6, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8330 ### Description Currently, tables created in AppFlowy cannot be exported directly to Excel (.xlsx) format. For users who use AppFlowy to manage structured data — such as logs, project tracking, or automation input — it would be extremely useful to export tables into Excel files. Proposed features: 1. Manual export: • Allow users to manually export any table (or database view) as an .xlsx file. • The export option could appear in the table’s menu (e.g. “Export → Excel”). • Each export should preserve column headers, formatting, and data types. 2. Automated export (integration support): • Allow exporting tables automatically through integrations such as Zapier, Make (Integromat), or AppFlowy API hooks. • Example use cases: • Export a table to an Excel file daily. • Trigger an export whenever a new row is added or updated. • The exported file could be saved to a user-specified folder or cloud storage (e.g. OneDrive, Google Drive, Dropbox). ### Impact Makes AppFlowy much more compatible with existing workflows that depend on Excel files. • Allows users to reuse AppFlowy data in automated processes, reports, and analytics tools. • Reduces manual work for users who periodically need to sync AppFlowy tables with other systems. • Increases productivity for developers, analysts, and makers who rely on Excel-based automations. • Enhances integration potential with third-party automation platforms. ### Additional Context often use AppFlowy tables to organize project or workflow data, and I need to periodically process that data in Excel-based automation scripts. Having both manual export and automatic export via Zapier or similar tools would make AppFlowy an even more powerful productivity platform. Example scenario: • I maintain a project status table in AppFlowy. • Once a day, or when new data is added, the table is automatically exported to Excel and processed by an external automation script.
Author
Owner

@LucasXu0 commented on GitHub (Nov 7, 2025):

Table
Image

Database
Image

Is it your expectation to have an xlsx export in these 2 places?

<!-- gh-comment-id:3500198468 --> @LucasXu0 commented on GitHub (Nov 7, 2025): Table <img width="826" height="682" alt="Image" src="https://github.com/user-attachments/assets/a75efeb4-ad04-4246-84f3-a87d346c47a3" /> Database <img width="514" height="228" alt="Image" src="https://github.com/user-attachments/assets/3383a062-146a-40fe-8808-871d7544dc13" /> Is it your expectation to have an xlsx export in these 2 places?
Author
Owner

@KriszDK commented on GitHub (Nov 7, 2025):

Yes something like that.

<!-- gh-comment-id:3503027957 --> @KriszDK commented on GitHub (Nov 7, 2025): Yes something like that.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#3733
No description provided.