Bulk planning and CSV imports
Generate a plan or import rows, review the preview and schedule a checked batch.
Bulk Fill helps prepare several posts together. The current planning screen includes a brief, account selection, cadence, date range, posting window and a preview step. It also offers CSV import and a downloadable template.
Build a plan from a brief
-
Open Create → Bulk Fill. In What to post about, describe themes, goals and the angle you want.
-
Under Platforms & cadence, select the exact connected accounts. Check every account name.
-
In Amount & schedule, choose posting days, start/end dates and the posting window. Read the timezone displayed on the form.
-
Choose the offered media mode. If using generated images, review the resulting assets individually.
-
Use Advanced settings to tune Educational, Promo, Engagement, Personal and Reshare content mix; brand voice intensity; focus topics; topics to avoid; and hashtag behavior. Add source notes or reference URLs when helpful.
-
Choose Generate preview. This is your review stage, not evidence that everything has published.
Import a CSV instead
Choose Download template from this workspace's screen. Keep its required headers and fill the rows using the formats it specifies. Check exact account identifiers, scheduled timestamps, captions and media URLs. Do not rely on an old template from another version. Upload through Import CSV and inspect the parsed preview. Treat an empty or ambiguous schedule as an error until you understand the resulting action. Remove placeholder text and fix unsupported media before confirming.
Review and commit
Read every row's account, full caption, attachments, date and timezone. Edit or skip unwanted rows and resolve warning or error messages. Check the final count and any usage estimate, then use the explicit save or scheduling action offered. Open Calendar to confirm the resulting items and approval states. For partial failures, compare successful rows with the failed-row report before re-importing. Retry only confirmed missing items; do not assume a repeated upload is always duplicate-safe.