How it works
From idea to published, with nothing left to chance.
- 01
Capture
Ideas go into a backlog with notes and tags. When one is ready, turn it into a draft with a template or the outline builder.
- 02
Write
Draft in the editor. Autosave runs every few seconds, versions are kept, and the checklist marks anything unfinished, including leftover template prompts.
- 03
Review (teams)
Request a review. A reviewer approves the exact text or asks for changes. If the workspace requires approval, scheduling is blocked until the current text is approved.
- 04
Schedule
Pick a local date and time. Pilcrow stores the exact UTC moment and your time zone, and asks you to resolve daylight-saving gaps or repeats.
- 05
Confirm
You see the destination, the exact content and its caption, the local time and the method, and you confirm. It is always one post: Pilcrow never adds an announcement. That confirmation is recorded.
- 06
At the minute
A durable job wakes up, checks the schedule is still valid and claims it exactly once. For Articles today, that means your reminder goes out with everything ready.
- 07
Publish and confirm
You paste the Article into X, press Publish and paste the link back. Only then is it marked published, tracked for analytics and ready to repurpose.
What X allows, and what we do about it
We checked X's developer documentation on 30 October 2026:
- X documents endpoints to create an Article draft and to publish it. There is no documented way to edit a published Article or to schedule one natively.
- The X API is billed per use with prepaid credits. Prices for the Article endpoints are not listed, and account eligibility is not documented.
- Ordinary posts can be created through the API, at a listed price per post, with stricter rules for automated replies on self-serve plans.
So Pilcrow publishes Articles in assisted mode today, and ships the automatic path switched off until paid access and eligibility are verified with a real account. When that happens, nothing about your drafts, calendar or history changes.
Pilcrow never drives the X website with a robot, never reads your cookies and never uses undocumented endpoints.
Reliability, plainly
- Jobs never run early. They run at the scheduled minute or shortly after; each attempt records how many seconds late it started.
- If the same job is delivered twice, only one delivery does anything.
- If X does not answer after a post was sent, Pilcrow marks it as needing a check rather than retrying and risking a duplicate.
- If a scheduled message is lost, a backup sweep picks the job up.