Skip to main content

Scheduled Exports

Lists have no export button on screen; a scheduled export is how a list leaves as a file. An admin defines a schedule — which resources (errors, leads, recordings), how often (daily, weekly or monthly), and who is told — and the platform generates the files overnight and mails the recipients a link.

Creating a Schedule​

Settings → Exports (site admin). Pick the resources, the cadence and up to five recipient addresses.

A new schedule is created switched off and runs only after you enable it — a schedule sends people email, so nothing mails anyone until an admin has explicitly said so. The first run happens at the next run hour (05:00 UTC), never immediately, so an accidental toggle does not fire a mail.

What the Files Contain​

Each run produces one gzipped CSV per resource, generated by the same exporter as the API's export routes: the same columns, the same 50 000-row ceiling with an explicit # truncated marker, and the same protection that keeps a spreadsheet formula typed into a form inert when the file is opened in Excel.

One deliberate difference: the raw form fields column — the unaudited remainder of a lead, available interactively to admins only — is never included in a scheduled file, because a scheduled file is opened by whoever reads a mailbox.

Delivery and Retention​

Recipients receive an email with a link to the dashboard, never the file itself — the download sits behind your sign-in and the site's own access control, so forwarding the mail forwards nothing.

Generated files are kept for 7 days and then removed automatically, files and records together. A file is a copy of personal data the platform already holds under its own retention windows, and copies are not kept longer than they are useful. An expired link reports the file as expired.

Roles​

ActionMinimum role
Create, change, enable or delete a scheduleadmin
See schedules, list files, download a filemember

Downloading hands over the whole table, which is why member is the floor — the same bar as the API's export routes; a viewer cannot take at scale what their screen refuses one page at a time.