← monday Scheduled Excel Export
monday Scheduled Excel Export, published by Cody Labs. Effective 1 November 2026.
monday Scheduled Excel Export (the "app") exports selected monday board data into an Excel workbook and attaches it to an item update. Version 1 supports attachment delivery inside monday only. Email delivery is deferred and is not available in this version.
me API.The app runs on monday code, monday.com's hosted server-side infrastructure, operated for this app by Cody Labs. It reads data through monday's API, generates the workbook in memory, and uploads it to the chosen monday item update. The resulting attachment is stored in your monday account and follows that item's access permissions. This version does not send workbooks to SendGrid or another email provider.
Cody Labs maintains the application and may access its operational records for support and troubleshooting. We do not sell board data or use it for advertising. The fact that processing uses monday's infrastructure does not mean the app has no access to the data it processes.
Existing workflow exports use the short-lived API token supplied with a verified monday action request. A separate manual Board View is in development and is not yet enabled for public use. When that flow is enabled and you choose Connect monday, it will store an OAuth access/refresh token pair, encrypted and bound to your verified account and user, in monday-hosted Document DB. Encryption keys are kept separately in the server's secret storage. OAuth API tokens are not returned to the Board View.
The manual flow uses a temporary, necessary browser cookie to verify its authorization callback, plus single-use connection/export requests. The cookie lasts up to five minutes. Request records contain identity, expiry and request-verification information; connection state also temporarily holds the PKCE verifier used for OAuth. Expired OAuth state is scheduled for cleanup each minute while the enabled service is running; cleanup is retried after an outage. No advertising cookie is needed for this flow.
The app requests boards:read and updates:write for board reads and attachment delivery. The manual OAuth flow additionally requests me:read to verify the connected identity. Access remains subject to the scopes granted and that user's monday permissions, including shared boards they can access.
Scheduled Excel Export is developed by me (Cody Labs). It runs on monday code, monday.com's hosting for apps. Everything it stores is kept inside monday: mainly in monday's Document DB in the monday code environment for this app, plus one small legacy copy of the Free plan board record (and, for an account that used an earlier version of the app, old run records) in monday's key-value Storage for the app. It is not copied to any other service. Version 1 does not send email, so no email provider receives your data.
Board data is not kept. When an export runs, the app reads the board you chose through monday's API and builds the Excel file in memory. It attaches the file to the item update you chose and then discards it. The file you receive is stored by monday on your item update and follows monday's own retention, not ours. Disconnecting the app does not delete attachments already on your items.
What the app does store:
| What | Why | How long |
|---|---|---|
| Run records: your monday account ID, board ID, target item ID, number of rows exported, time, success or failure, the error message if it failed, monday's run IDs and the ID of the update the file was attached to | An audit trail, support, and stopping a retried run from attaching the same file twice | At most 90 days from the run. An hourly deletion pass removes older records; if a pass fails, the next one retries, so a record is never kept longer than 90 days plus the time until a pass succeeds |
| Encrypted connection credentials for the manual export view: the access and refresh tokens monday issues when you connect your monday account, with your account ID and user ID | Letting the manual export in the board view act on your behalf | Until you select Disconnect or the app is uninstalled. They are encrypted with AES-256-GCM using a key held in monday's secret storage, never in the database and never sent to your browser |
| Short lived request records: your account ID, user ID and a one time ticket or sign-in state used to protect the manual export and the connection flow | Preventing forged or repeated requests, and rate limiting | Minutes. They expire after 5 minutes and expired records are swept automatically |
| A Free plan board record: your account ID, the ID of the one board used on the Free plan and the date it was chosen. Held in Document DB, with a legacy copy in monday Storage (board ID and date only) | Enforcing the one board limit on the Free plan, so it cannot be reset by reinstalling | For as long as the app exists. It contains no board content. It is not removed by the automatic uninstall cleanup. Ask us to delete it and we remove both copies |
| Older run records and delivery markers, only for accounts that used a version of the app before the Document DB move: the same fields as run records above, held in monday Storage under the account | The same audit and duplicate-delivery purpose | Until we remove them. The automatic 90 day deletion and uninstall cleanup do not reach monday Storage, because it needs a live token for the account. We remove them by hand with monday's own storage:remove-data command, for the accounts concerned, after uninstall or on request |
| Operational log lines in monday code's application logs: your account ID with counts when an uninstall cleanup runs, and request metadata such as path, status and timing. They never contain credentials, board data or file contents | Running and troubleshooting the service | For as long as monday code keeps application logs. We do not copy them anywhere else |
We do not store the names or contents of your items, your column values, or the contents of the files we generate.
For the manual connection, Disconnect stops use of the stored connection and attempts to revoke both OAuth credentials. Each credential pair is removed after its revocation is confirmed. Failed cleanup retains encrypted credentials for retry; a background worker also retries abandoned connection attempts. Minimal account/user and connection-revision metadata can remain after Disconnect to reject stale authorization callbacks; uninstalling the app deletes that record too. Active OAuth credentials are not deleted solely because an access token expires, since the refresh credential may still be valid.
When you uninstall the app, monday notifies it, and the app then:
The exceptions are the Free plan board record described above (both copies) and anything in monday Storage from older versions, which is removed by hand as described in the table. Excel files already attached to your monday items are yours and stay in monday until you delete them.
Tokens are encrypted at rest. Requests from monday are checked against a signature before the app acts on them, and the manual export only accepts requests tied to a verified monday session. Revoking the app's access in monday at any time also stops it from using your connection.
Email [email protected] with your monday account ID and I will delete anything the app still holds for your account, including the Free plan board record. Please do not send passwords, API tokens or complete confidential workbooks in a support message.
The app uses monday.com's authorization service, GraphQL/file APIs, hosted app runtime, app storage and Document DB. Email delivery and SendGrid are not used in version 1. See monday.com's privacy policy for the platform's own handling of account data and attachments.
We may update this policy; material changes will be reflected by the effective date above.
Questions about this policy: [email protected].
monday.com and Excel are trademarks of their respective owners. This app is independent and not affiliated with or endorsed by either.