Agorapulse

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the social publishing and inbox tool I actually need instead of Agorapulse.

The constraint that shapes everything: **network APIs are the whole difficulty.** They are restricted, they change, they require app review, and some of what these tools do is available only to approved partners. Build for the networks that let you in and be explicit about the rest.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode
- A worker process for publishing and polling
- Caddy in front

THE DATA MODEL
- accounts: id, network, handle, token_encrypted, refresh_token_encrypted, expires_at, scopes, status
- posts: id, body, media_ids_json, created_by, status
- targets: id, post_id, account_id, scheduled_for_utc, published_at, remote_id, status, error — **one row per network, because the same post succeeds on one and fails on another and a single status hides that**
- variants: per network overrides — length, mentions, first comment, alt text
- conversations and messages: id, account_id, remote_id, kind, author, body, at, assigned_to, status
- metrics: id, target_id, name, value, collected_at — sampled over time, since networks revise numbers for days

PUBLISHING RELIABLY
- The queue is a table with a lease; a crashed worker's job is reclaimed
- **Idempotency on every publish**, keyed by target id, and check the remote before retrying. Posting twice to a public account is a visible, embarrassing failure and retries are what cause it
- Per-network validation before scheduling — length, media counts, aspect ratios, mention syntax — with the errors shown at composition time and not at publish time
- Token refresh in the background with an alert well before expiry. **A silently expired token means a fortnight of posts that never went out**, which is the classic failure of homemade schedulers
- A visible queue with failures at the top and a one-button retry

THE INBOX
- Poll comments and messages where the API allows, store with the remote id, and never lose one to a redelivery
- Assignment, a status, and an internal note. Two people replying to the same comment is what an inbox exists to prevent
- Saved replies, and a keyboard-first list. Speed is the whole feature

REPORTING HONESTLY
- Collect what the API gives, on a schedule, and store each collection rather than overwriting. **Networks revise engagement numbers for days after a post**, and only a series shows that
- Report reach and engagement with the collection date attached
- Do not invent a composite score. It hides which number moved

ACCESSIBILITY AND CARE
- Alt text required on every image before scheduling. It takes ten seconds and it is the difference between a post everybody can read and one many cannot
- A preview per network, because a post that looks fine in the composer wraps badly on half of them

WHAT MATTERS MOST
Per-network target rows and idempotent publishing. The first makes failures visible; the second stops the retry doing damage.