X
The X group turns public account activity into rows.
- Actions
- 3
- Category
- Lead Sourcing — Scrape
- Authentication
- SyncGTM credits — no external API key
- Cost
- 0.3 credits per post or profile
- Returns
- Posts, engagement counts, or commenter accounts
Available scrapers
| Scraper | Input | What it returns |
|---|---|---|
| Profile Posts | Handle or profile URL | Recent posts with content, engagement and timestamps |
| Profile Reactions | Profile URL | That account’s posts with likes, retweets, replies and views |
| Post Commenters | Post URL | The accounts that commented on that post |
X is a SyncGTM native integration — it runs on SyncGTM credits, so there is no X account or API key to connect.
How to use it
- Copy the handle or post URL you want to work from
- Open the table and click Table → Import → X, then pick the scraper
- Paste the input and set a result limit
- Run it, map the fields to columns, and click Create Rows
- Enrich commenter handles — Person Twitter Profile links a handle back to a person
Common use cases
- Work a thread about your category. Commenters on a “what do you use for X” post are a warm list.
- Personalize from a founder’s own posts. Profile posts give you a real line to open with.
- Find which of their posts landed. Profile reactions rank an account’s output by engagement — useful when writing to a creator or picking what to reference.
- Track a competitor’s announcements. Their profile posts, in a table, with timestamps.
Best practices
- Choose threads about the problem rather than about a vendor — they draw buyers, not fans
- Filter commenters by bio before enriching; large threads pull in accounts with no company attached
- Handles are not people — enrich to a name and company before you treat a row as a lead
- Dedupe on handle across threads in the same niche
- Keep the post URL so the reference in your first message stays traceable
Where to next
- Person Twitter Profile — link a handle to a person
- Company X (Twitter) — find the handle for a company you have
x_post_commenters— run it from an AI client over MCP