PostEaseHow to export your posting history to CSV
One row per platform a post targeted, with a timestamp format that still makes sense once the file has left the app.
Published Aug 30, 2026
1. Five columns
caption, platform, status, scheduled_at, published_at
2. One row per platform a post targeted
A post scheduled to 3 channels is 3 rows, not one. Each channel's status and timestamps are independently true; collapsing them into a single row would either drop information or invent a status that never existed.
3. Timestamps that still make sense outside the app
Full year and an explicit numeric UTC offset on every timestamp, not the shorthand the calendar shows on screen. The file is meant to outlive the browser tab it came from.
4. Your whole history, not a date range you have to pick
Every post in the workspace, every time. There's no start/end date to choose and nothing to page through. A partial export defeats the point of a record.
More guides
How to connect PostEase to Zapier or Make
Every publish can POST a signed payload to a Zapier Catch Hook or a Make custom webhook, carrying the caption, the account and a link to the live post. No app listing needed, and you can send a test event to map the fields.
Connecting PostEase to the rest of your stack
The outbound webhook, Zapier and Make, importing a calendar from another scheduler, and the browser extension are one integration surface, not four separate things to discover on your own.
Adding alt text to the images you schedule
One field in the composer, sent to X, LinkedIn, Pinterest, and Bluesky with the image. What it is for, what the 500-character cap comes from, and why video is left out.
How to set your workspace timezone
Every time you see or type in PostEase is in one zone chosen for the workspace, not your browser’s. Posts already scheduled keep their exact time when you change it.
Keep your own record of what went out.
Every channel you have, included. Adding another does not change the price.