The problem
An agent can write ten posts in a minute, but someone still has to copy each one into a platform at the right time. Giving every post a timestamp by hand is the same chore in a calendar.
How it runs
- 1You create a collection and a schedule: weekdays at 09:00, your X channel and your n8n workflow, "the next waiting post".
- 2Your agent calls create_post five times; the drafts wait in the collection.
- 3Every morning the schedule publishes the oldest draft to both channels and records the links.
- 4When nothing waits, the schedule records a request. The agent sees it in list_requested_work and writes the next batch.
- 5You glance at the calendar on your phone and drag a post to another day when the news changes.
Result
The agent writes, staqly keeps the rhythm, you keep the final say on the calendar. Nothing is copied by hand.
MCP tool calls
# the agent, oncecreate_schedule {"collection":"Daily tips","name":"Weekday mornings", "kind":"recurring","rule":{"times":["09:00"],"weekdays":[1,2,3,4,5],"tz":"Europe/Warsaw"}, "channels":["ch_x...","ch_n8n..."],"pick":"next","source":"agent"}# every nightcreate_post {"collection":"Daily tips","content":"Tip: drag a post on the calendar to move it.", "targets":[{"channel_id":"ch_n8n..."},{"channel_id":"ch_x...","content":"Drag a post to move it."}]}# when the collection runs drylist_requested_work → {"kind":"posts","schedule":{"name":"Weekday mornings"}, ...}Read the full recipe