SMF·TAPLIO
Can a prompt replace Taplio?
Social media — social scheduling and content repurposing
Exhibit tracking slip
Verdict
Two of Taplio's three pillars are simply not available to a personal build. The inspiration feed is a database of high-performing LinkedIn posts, which LinkedIn's API does not expose and which exists because somebody collected it at scale; lead search is the same problem again. What remains — scheduling your own posts and keeping notes on people you want to stay in touch with — is real and useful, and it is a fraction of the product.
Exhibit A — The prompt
Received on31.07.2026Build a personal LinkedIn publishing and follow-up tool using only LinkedIn's official API. No scraping, no browser automation, no unofficial endpoints.
Authentication: register a LinkedIn developer application, request the member share permissions, and run the documented OAuth flow. Store tokens encrypted and surface a clear reconnect prompt on expiry. State in the README which permissions the application needs and that LinkedIn's review process gates them.
Publishing: a composer with LinkedIn's real character limit, a preview showing where the see-more truncation falls (which is the one formatting decision that matters on the platform), image and document attachment with size validation, and a queue with a weekly slot grid. A background worker publishes at the scheduled time with an idempotency key and stores the returned post URN.
Metrics: for each published post, poll whatever the official API exposes for that permission level and store readings over time. Show exactly what is available and label clearly anything LinkedIn does not return, rather than filling gaps with estimates.
Follow-up list, which is the second half of this build. A private table of people: name, profile URL entered by hand, how you know them, a free-text note, and a follow-up interval. The dashboard shows who is overdue. Logging an interaction resets the clock. This is a personal CRM you type into — it never reads LinkedIn's member data, never scrapes a profile, and never sends anything on your behalf.
Content library: saved drafts, reusable openings, and a swipe file where the user pastes posts they liked with their own note on why. Manual entry only.
Out of scope, and say so plainly: any collection of other people's posts or profiles, lead search, automated connection requests, automated commenting or liking, and any browser extension acting inside LinkedIn. Those behaviours breach LinkedIn's terms and get accounts restricted; the build refuses them by design rather than by omission.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the database of high-performing posts you browse for ideas
- B.2 lead search and the ability to filter LinkedIn's member base
- B.3 engagement metrics on posts beyond what the official API returns
- B.4 the browser extension that works inside LinkedIn itself
Prior art
Exhibit C — Why people still pay: API access, connector upkeep, and collaboration
Because the inspiration feed is the product for most subscribers, and it is a dataset somebody assembled at a scale and a legal posture that a personal tool cannot match.
Questions
Can I import my Taplio content?
Drafts and scheduled posts export as text and come across fine. The inspiration feed and any lead lists do not, and would not be usable here anyway — this build has no place to put other people's posts except the manual swipe file.
Why not just scrape LinkedIn for the inspiration feed?
Because it breaches LinkedIn's terms and the usual consequence is a restricted account, which for someone using LinkedIn professionally is a far larger loss than a subscription. The prompt rules it out as a design decision, not an oversight.
What does it cost to run?
A small VPS with PostgreSQL, five to ten dollars a month. The LinkedIn API is free at personal posting volumes. The real cost is the API approval process, which takes time and can be refused.
What is the one thing that does not survive the rebuild?
Ideas. People subscribe to Taplio to browse what worked for others in their niche this week. Nothing in a personal build produces that, and a swipe file you fill in by hand is not the same thing at all.
Related tools
Receipt