Zilfu for X

The Twitter scheduler
that never misses.

Queue two weeks of tweets in one sitting, then close the tab. Zilfu publishes to X on time, keeps pulling impressions and bookmarks after it lands, and never forgets the 9am slot. Two accounts free, no card.

Connect X free → Read the docs
L
@lumenstudio
X · Scheduled tweet
Scheduled

Hot take: shipping daily beats shipping perfectly. Here's the proof… 🧵

Mon · 9:00 AM Smart Slot
POST /v1/posts 
{
  "content": "Hot take… 🧵",
  "networks": ["x"],
  "schedule_at": "Mon 9:00"
}
✓ scheduled 200 OK · 142ms
  • Skip the daily X ritual
  • X analytics on every plan
  • Impressions you can actually track
  • Crosspost without copy-paste
— What you get

Built for the way you use X.

Schedule tweets weeks ahead, crosspost without copy-paste, and see what actually moved the needle — all without opening X.

01 — Schedule

Queue today. Forget tomorrow.

Stack two weeks of takes in one sitting and step out of the daily refresh loop. Zilfu publishes the moment you've planned for, even when you're deep in something else.

Get started free →
Up next this week 12 scheduled
Tue · 6:15 PM+ photo

Sneak peek of what we shipped this week

Photo
Wed · 12:00 PM280 chars

Quick update on the new redesign — what we kept, what we tossed

Tweet
Fri · 8:00 PM28s clip

Watch what happens when agents ship code on their own

Video
02 — Compose

Write once. Post everywhere.

Compose one post, pick your destinations, and Zilfu publishes everywhere at once. X, Threads, Instagram, Facebook, LinkedIn, TikTok, and Pinterest — all from a single composer. No copy-paste, no tab-juggling.

Get started free →
New post Saved · just now

Hot take: shipping daily beats shipping perfectly. Here's the proof…✨

Publishing to
𝕏 @lumenstudio X
@ @lumenstudio Threads
IG @lumenstudio Instagram
Li Lumen Studio LinkedIn
03 — Measure

Track every impression, repost, bookmark.

Impressions, reposts, replies, quotes, bookmarks, and likes — broken down per tweet. Refreshed every four hours, ready when you open your laptop. No CSV exports. No spreadsheets.

Get started free →
Impressions 38.4K +41%
Reposts 412 +22%
Bookmarks +189 +8%
Tweet impressions · last 30 days X
— What you can post

Everything X supports, scheduled.

Schedule single posts or full multi-tweet threads — write the whole chain once and Zilfu publishes it in sequence.

Post types

  • Posts — A single post with text and media.
  • Threads — A multi-post chain, queued and published in order.
  • Media — Images and video attached to any post.

Limits & rules

  • Caption: up to 280 characters
  • 280 characters per post — longer if you have X Premium.
  • Links and media still count toward what readers see first.

Recommended sizes

  • Post image — 1600 × 900
  • Header — 1500 × 500
Full X size guide →

X tips that earn reach

  • Make the first post a hook strong enough to earn the click.
  • Thread long ideas instead of compressing them into one post.
  • Native images and video out-reach plain links.
  • Size post images at 1600 × 900 (16:9) to display uncropped.
— How it works

From zero to scheduled in under a minute.

Three steps. Then the rest of your week takes care of itself.

1

Connect in one click.

Sign in with X, pick the account you want Zilfu to manage, and grant the standard permissions. That's the whole setup — OAuth 2.0 with PKCE, no password ever shared.

2

Drop in your tweet.

Compose in the dashboard, or trigger from Zapier, n8n, your CMS, your AI agent — anything that talks HTTP.

3

We publish. You watch.

Posts go out at the right time. Impressions, reposts, and bookmarks roll in every four hours. Webhooks fire on publish, fail, and reply.

— For developers

Automate with APIs.

Your CMS, your AI agent, your automation tool — anything that talks HTTP can ship a tweet to Zilfu. Multi-tweet chains, webhooks, and an MCP server included.

142ms 
# Schedule a tweet to your X account.
curl -X POST https://zilfu.app/api/posts \
  -H "Authorization: Bearer sk_live_xxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hot take: shipping daily beats shipping perfectly 🧵",
    "networks": ["x"],
    "schedule_at": "2026-04-23T18:15:00Z"
  }'
# Add Zilfu's MCP server to Claude, Cursor, or any agent.
{
  "mcpServers": {
    "Zilfu": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://zilfu.app/mcp/social-media",
        "--header",
        "Authorization: Bearer ${SOCIAL_MEDIA_TOKEN}"
      ],
      "env": {
        "SOCIAL_MEDIA_TOKEN": "<paste your api token>"
      }
    }
  }
}
✓ Response · 200 OK
{
  "id": "post_8aB3xY9k",
  "status": "scheduled",
  "scheduled_at": "2026-04-23T18:15:00Z",
  "networks": [
    { "name": "x", "status": "queued" }
  ]
}
No upgrade needed

Full API on the free plan. Same endpoints, no surprises.

No servers to run

Hosted MCP server — drop the URL into Claude, Cursor, or any agent.

Real events

Webhooks fire when tweets publish, fail, or get scheduled.

— FAQ

X, asked and answered.

A Twitter scheduler is a tool that publishes posts to X (formerly Twitter) at a time you choose instead of the moment you write them. You draft in advance, pick a date and time — or drop the tweet into a recurring weekly slot — and the scheduler posts it for you. Zilfu is a Twitter scheduler that also covers Threads, Instagram, Facebook, LinkedIn, TikTok and Pinterest from the same queue.

Zilfu's Free plan connects 2 social accounts with no credit card and no trial clock — so if X is one of them, scheduling tweets is genuinely free. Analytics are included on the Free plan too. Paid plans start at $19/mo when you need more than 2 accounts.

X has a built-in scheduler, and if you post from one account on desktop it may be all you need. Zilfu earns its place when X is one of several accounts: one queue and calendar across seven networks, recurring weekly slots so you fill a time rather than pick a timestamp, analytics that keep collecting after the post goes out, approvals before anything publishes, and a REST API plus MCP server for scheduling from code or an AI agent.

No — any standard X account works. Zilfu connects through X's official OAuth 2.0 flow with PKCE, so your password never leaves X.

Through the API or the MCP server, yes — a post accepts child posts and Zilfu publishes them as one linked chain. The web composer schedules single tweets; multi-tweet threads are built programmatically for now.

Yes — by spinning up a workspace for each account. Every workspace stays isolated with its own queue and scheduling slots, and you switch between them in one click. Workspaces are unlimited on every plan, including Free; what scales with the plan is how many accounts you can connect in total (2 on Free, up to 300 on Scale).

Yes. Scheduled tweets sit in your queue until publish time — edit the text, swap the media, change the time, or cancel entirely whenever you like.

Impressions, likes, reposts, replies, quotes, and bookmarks — pulled from X every four hours and rolled up per tweet. Impressions is the default headline metric. Note: a few of the deeper organic metrics depend on the API access tier on the connected X account; the public counts are always available.

We never see your password — Zilfu connects through X's official OAuth 2.0 flow with PKCE and only requests the scopes needed to publish on your behalf and read your posts and engagement. You can revoke access from your X settings → Connected accounts at any time.

Your whole social, handled.

Plan, approve and publish every account from one place.
Free to start, no card needed.

Start now for $0