Bulk Editing & Posting

Plan a month of content in one sitting. A bulk session is a spreadsheet-style grid where you draft many posts side by side, edit them together, and schedule the whole batch when it's ready.

How it works

Create a session, add rows, fill them in. Each row is one post: its accounts, content, media, tags, and time. Rows stay drafts until you schedule them.

The important difference from the single-post form: drafts don't have to be valid. Leave a row half-finished, come back tomorrow, fill in the rest. Validation runs when you click Schedule. Every row that passes is scheduled; a row that doesn't stays a draft, with its error shown on the row, so you can fix it and schedule it again.

Sessions are named and kept, so you can work on "October campaign" over several days and rename it later.

Editing many posts at once

Select rows and apply a change to all of them — add the same accounts, apply a set of tags, set a post type. The bulk toolbar edits the same fields the single-post form does, so nothing behaves differently just because it was set in bulk.

Each row shows its own validation state as you go. A row that won't schedule tells you which field is the problem, on the row, before you try.

Scheduling the batch

Click Schedule and every draft in the session is validated. Each row that passes is queued for its own time — rows keep their individual schedule times, so scheduling the session doesn't publish them all at once. Rows that didn't pass stay in the session as drafts until you fix them.

After that they behave like any other scheduled post: editable, cancellable, and tracked through the same statuses. See Scheduled Posting.

Good to know

• A draft with no accounts, or with fields still empty, is a normal work-in-progress state — not an error.
• Media attached to a draft row is stored when you attach it, so it's ready whenever you schedule.
• Buttons in the grid that sort, delete, or manage media don't submit the form — you can rearrange freely while drafting.

Where it works

Bulk sessions aren't app-only. The same operations are available through the API and over MCP from an AI assistant — create a session, add posts to it, update them, and schedule the session when it's ready.

One difference when adding posts through the API or an assistant: media is downloaded and checked as each post is added. A post whose file can't be used at all (corrupt, or a format we can't process) is skipped rather than saved as a draft, and the response tells you which ones and why.

That combination is the fastest way to build a content calendar: describe the month to Claude or ChatGPT, let it fill the session, then review the grid in the app and hit Schedule.