App Logo
x.com

X (Twitter) login (Google SSO)

Log into X (Twitter) with Continue with Google, picking the given Google account in Google's sign-in window, and land on the X home timeline. Returns straight away if already signed in, and reports the X handle that is signed in. Needs a browser that is already signed in to that Google account.

Input

email required

The Google account (email) linked to the X account to sign in with. Picking an account that has no X account opens X's sign-up flow instead.

Output

already required
loggedIn required
stage optional
handle optional
userId optional

FAQ

Log into X (Twitter) with Continue with Google, picking the given Google account in Google's sign-in window, and land on the X home timeline. Returns straight away if already signed in, and reports the X handle that is signed in. Needs a browser that is already signed in to that Google account.
Required: email.
It returns stage, handle, userId, already, loggedIn.
Yes. It acts as you on x.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the x.com cookies saved by the Reduck extension.
It makes changes on x.com, like sending, posting or booking something.
Ask an AI agent connected to Reduck to run reduck/x.com/login_with_google, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/x.com/login_with_google
It is part of Reduck's official curated catalogue.

Related scripts

x.com

Search X tweets

Search X for tweets, supporting all X search operators; the tab arg picks 'top' (ranked sample, default) or 'latest' (chronological). Returns per tweet a canonical record: id, url, author {id, handle, name}, text, created_at, lang, likes, retweets, replies, quotes, bookmarks, views, is_retweet, is_quote, plus followers (the author's follower count, a search-only enrichment), and the top-level query and count. Top is a ranked sample, not exhaustive.

x.com

Get X tweet

Fetch a tweet by URL — the focal post plus the surrounding conversation. Returns `tweet` (the focal post; null if deleted/tombstoned) and `replies[]`, which holds every other tweet on the conversation page: both the focal's ancestors (the thread above it, present when the focal is itself a reply; each has `in_reply_to` null or pointing above the focal) and the replies below it (`in_reply_to` points at the focal or a sibling reply). Use `in_reply_to` to tell ancestors from replies and rebuild the thread — the array is not filtered to descendants of the focal. Each entry is a canonical tweet record: id, url, author {id, handle, name}, text, created_at, lang, likes, retweets, replies, quotes, bookmarks, views, is_retweet, is_quote, in_reply_to {id, author_handle}. Scrolls the main thread until `count` is met (then complete=false — more may exist) or it drains (complete=true). Replies behind a "Show more replies"/hidden/probable-spam cursor are not expanded, so even complete=true is a floor, not a guarantee every nested reply was seen.

x.com

X (Twitter) posts API: export a user's tweets with views and likes

An unofficial X (Twitter) API for a user's posts: export an account's latest tweets with their views, likes, reposts, replies, quotes and bookmarks as data, in one call, without the X API. For the owner-only analytics of each post (impressions, engagements), run get_post_analytics on its id. Get a user's latest posts by handle (x.com/<handle>, the Posts tab), newest first: their own tweets and self-threads, without replies (see get_user_replies) or reposts (see get_user_reposts). Works signed in or signed out. Signed in, it reads the full Posts tab up to count. Signed out, X only shows visitors its few most recent posts, so it returns that short preview and fewer than count is expected; each post's source field says which one you got. Returns per tweet: id, url, text, created_at, lang, likes, retweets, replies, quotes, views, bookmarks, is_retweet, is_quote, source.

Start building not clicking

Get started for free