The methods side by side
| Method | What it does | What starts a post |
|---|---|---|
| The weekly queue | Add weekly time slots, then add posts to the queue and each takes the next free slot. | A slot comes round |
| Repeating posts | Repeat a post from every day to every month, with versions that rotate where a network refuses identical repeats. | The interval you set |
| RSS to posts | Turn each new item in a feed into a post from a template. Items are saved for review, or auto-queued with a daily limit. | A new item in a feed |
| CSV import | Load up to 500 posts from a spreadsheet. Every row is checked against its network before anything is queued. | You import a file |
| The API | Create and schedule posts from your own code with a key bound to your workspace. | Your code calls it |
| Webhooks | Receive a signed message when a post publishes, fails or needs attention, and act on it in your own systems. | A post event |
| The MCP server | Let an assistant list accounts, write and schedule posts and read results, with the permissions of the member who connected it. | An assistant asks |
Which method to start with
- You post on a steady rhythm: start with the weekly queue.
- You blog or publish on a feed: use RSS to posts and keep items for review.
- You plan in a spreadsheet: use CSV import with the content calendar template.
- You build products or run an agency stack: use the API and webhooks, or connect an assistant through the MCP server.
What stays in your hands
Automation here moves the work of choosing times and retyping, not the writing. Posts from contributors can wait in an approval inbox, feeds can be set to save items for review, and every post is checked against its network before it is queued, so automation does not send what a network would refuse.
Every plan, from $29 a month, includes the API, the MCP server and signed webhooks. See pricing.