Workflows5 min read
Bulk operations: project cloning, CSV import and the Cmd+K palette
Project cloning, CSV import of up to 1,000 rows, bulk scheduling through the API and the Cmd+K palette: the tools for setting up and filling many brands at once.
A single-post composer works well at the scale of one or two brands. At higher counts (ten, fifty), most operator time is spent setting up new projects, scheduling content in batches, and switching between projects. Postcrow has four primitives for that scale.
Project cloning
When you start a new brand whose tone is close to an existing one, cloning is faster than starting from scratch. In Settings → All projects, hover any project and click the copy icon. Enter a name for the new project.
The clone inherits:
- Timezone
- Description
- Brand voice paragraph
- Brand voice samples (so you can re-train later)
It does not inherit:
- Social accounts (each brand has its own OAuth tokens)
- Posts (each project has its own publishing history)
The clone is created in the same transaction as the new project. From the API, it's a POST to /api/projects with clone_from: <source_id>.
CSV import
The /app/import page accepts a CSV upload or paste. The format is intentionally simple to round-trip with Google Sheets, Notion exports, or any spreadsheet tool:
content,platforms,scheduled_at,media_urls
"Post body","bluesky,mastodon","2026-12-01T09:00:00Z",
"Another post","telegram","2026-12-08T09:00:00Z",
"Draft post (no schedule)","discord,mastodon",,Header columns can be in any order. Required: content and platforms. Optional: scheduled_at (ISO-8601; omit it to save as draft) and media_urls (comma-separated URLs).
Each row is validated. The import response returns counts of created vs skipped, with per-row reasons (empty content, unknown platform, past schedule date). The upper limit is 1,000 rows per import.
A common workflow: maintain an annual content plan in a sheet, export quarterly, drop the CSV in Postcrow, and the next three months are scheduled.
Bulk schedule through the API
POST /api/social/bulk with the bulk-schedule action takes a project, an array of posts and a date range. It spaces the posts evenly across the range and returns what it created and what it skipped:
POST /api/social/bulk
{
"action": "bulk-schedule",
"project_id": "<project ID>",
"posts": [{ "content": "Post body", "platforms": ["bluesky"] }],
"from": "2027-01-04T08:00:00Z",
"to": "2027-12-27T08:00:00Z"
}Posts whose scheduled time falls in the past are skipped and reported. The maximum is 500 posts per call. API keys require a paid plan (Pro, Agency or Platform).
Command palette
The Cmd+K (or Ctrl+K on Linux/Windows) palette opens anywhere in the app and fuzzy-finds projects by name. It also jumps to any of the app pages: Overview, Posts, Calendar, Accounts, Analytics, AI, Bulk import, Activity, Settings.
Arrow keys to navigate. Enter to select. Escape to close.
Combined workflow: onboarding a new brand
The four primitives chain naturally. Onboarding a new brand end to end, with a starter content calendar and auto-recycle (Agency and Platform plans):
- Cmd+K → switch to an existing brand whose voice is close to the new one.
- Settings → hover its row → Clone. Name the new project.
- Cmd+K → switch to the new project.
- Settings → Brand voice → paste 5 brand-specific samples → Re-train.
/app/import→ upload a CSV of starter posts → Import.- Settings → Auto-recycle → enable.
The new brand now has a queue, a voice, and a worker that keeps the queue alive.
Summary
Each primitive is small on its own. Together they turn setting up a brand into a short checklist instead of an afternoon of copy-paste, which is what makes running ten or more brands alone manageable.