Twitter Lead Generation: Find Buying-Intent Posts (2026)
Find people on X asking for a tool like yours. Buying-intent searches for Twitter lead generation, filters for job and giveaway noise, and Slack alerts.
Tarun Khatri
Published · Updated · 7 min read
Twitter lead generation works best when you search X for people asking for a tool like yours, then reply to them by hand.
This guide is for founders and sales teams who sell on X (Twitter). You get the searches, filters for the noise, alerts in Slack or your CRM, and what one real search returned. We run Weir, the API behind the alerts.
Paste this into X's search box, swap in your category, and pick Latest:
("alternative to" OR "recommend a" OR "switching from" OR "looking for a") CRM -hiring -giveaway -job lang:en
- List buying phrases"alternative to", "recommend a", "switching from".
- Search X by handAdd your category and read the Latest tab.
- Cut the noiseExclude job, hiring and giveaway posts.
- Run it by APIThe same search as JSON fields.
- Get new leads in SlackA monitor sends a signed webhook.
- Reply as a personAnswer the question before you pitch.
Step 1: Pick buying-intent phrases for Twitter lead generation
People who are ready to buy say so in a few set ways.
Pick phrases from each group and pair them with your category:
- Switching: "alternative to", "switching from", "moving off".
- Asking: "recommend a", "looking for a", "what do you use for".
- Comparing: "[tool] vs [tool]", "is [tool] worth it".
- Complaining: "[tool] is down again", "tired of [tool]".
Your category word does the targeting. Use the word your buyers use, like "CRM" or "invoicing app", not your product's own label.
Step 2: Find leads on Twitter with X's search box
Paste the query from the top of this page into X's search box. Each part does one job:
- Quotes keep a phrase together.
ORmeans any one of the phrases.- A minus sign drops posts with that word.
lang:enkeeps English posts.
Then pick Latest, so you see the newest asks first.
Our X advanced search builder writes these queries from a form. The search operators guide explains each operator.
Step 3: Cut the noise from your lead search
Every buying phrase also matches posts that don't come from buyers. These exclusions catch the common ones:
- Job posts:
-hiring -job, since recruiters write "looking for a" too. - Contests:
-giveaway. - Ads and promos:
-filter:links, though one long ad slipped past it in our test. - Side threads:
-filter:replies, which keeps original posts only.
Start with the first two, then add the others when ads and replies crowd your results.
Step 4: Run the search by API as a Twitter lead finder
Weir's search takes the same filters as JSON fields. An entry with a space, like "alternative to", is searched as a phrase:
curl -s https://api.weirapp.io/v1/x/search \
-H "Authorization: Bearer $WEIR_API_KEY" -H "Content-Type: application/json" \
-d '{"query": "CRM", "language": "en", "limit": 5,
"anyWords": ["alternative to", "recommend a", "switching from", "looking for a"],
"excludeWords": ["hiring", "giveaway", "job"]}'
We ran this on 22 October 2026:
None came from a brand account, so here are both runs' matches as types, not names:
| Match | A buyer? | Second run |
|---|---|---|
| Owner who found CRMs too pricey | Yes | Still found |
| Domain-for-sale ad | No | Still found |
| Reply about old CRM tools | No | Dropped |
| Stock post on the CRM ticker | No | Dropped |
| Affiliate promo with links | No | Dropped |
| SEO agency case study | No | New in run 2 |
The second run added "onlyText": true and "onlyOriginal": true, the API's names for -filter:links and -filter:replies. It also excluded $crm, the ticker, and cost 4 more credits.
Together, those changes dropped the reply, the ticker post and the promo.
A long promotional post still got through, links and all.
Step 5: Send new leads to Slack or your CRM
A monitor runs your search on a schedule and sends you only posts it hasn't sent before. Create a webhook first, as in our tweet alerts tutorial, then point a monitor at it:
curl -s https://api.weirapp.io/v1/monitors \
-H "Authorization: Bearer $WEIR_API_KEY" -H "Content-Type: application/json" \
-d '{"name": "CRM buyers", "schedule": "daily", "webhookId": "<your webhook id>",
"target": {"kind": "search", "sources": ["x"],
"query": "(\"alternative to\" OR \"recommend a\" OR \"switching from\" OR \"looking for a\") CRM -hiring -giveaway -job lang:en"}}'
- A monitor takes one
querystring. Type your operators into it, since it has noexcludeWordsfield. - Daily runs work on the free tier, with one monitor and one webhook, while hourly needs any $5 purchase.
- Each run reads one page of the newest matches, about 20 on X, so a busy search needs hourly runs.
- Deliveries are signed. Check the HMAC-SHA256 signature on the raw body, then forward the posts to Slack or your CRM.
That tutorial has the receiver in Python, and our n8n guide does the same check inside an n8n workflow.
What does Twitter lead generation cost with a monitor?
X lead generation by monitor is cheap: each run costs 1 credit, plus 1 for each new post it finds. Posts it already sent you cost nothing again.
Our CRM search found five matches in about a day. Here is a month at that pace:
Both fit inside your 5,000 free credits a month.
Hourly runs need a one-time $5 pack first. It adds 25,000 credits that never expire, and pricing lists the bigger packs.
Why you shouldn't automate replies, DMs or follows
Find leads with code if you like, but contact them by hand. X's developer guidelines set these limits on automated actions:
- Replies: "Only if user engaged first. Max 1 reply per interaction."
- Mentions: "No unsolicited @mentions."
- Direct messages: "Only after user DMs you first."
- Follows: "No bulk, aggressive, or automated following."
A person you found by search hasn't engaged with you, so a bot reply breaks the first rule. The same page's list of prohibited activities includes "Auto-replies to random users, bulk DMs, uninvited @mentions."
So reply as a person. Answer the question, say where you work, and leave your link out unless they ask.
If your lead search comes back empty or noisy
- Nothing matches. Add more buying phrases, since each one widens the search with
OR. - Every match is noise. Add the word that keeps showing up to your exclusions.
- Creating a monitor returns
409. Your tier's monitor limit is full, and the free tier allows one. - No deliveries arrive. Read the monitor's
/runs, and know that 20 failures in a row disable a webhook.
When not to use Weir
- You want a tool that replies or DMs for you. Weir is read-only, and X's rules ban that outreach anyway.
- Alerts must arrive in seconds. Monitors run hourly at best.
- One category, checked by hand, is enough. X's search box is free.
- Price per post is all that matters. TwitterAPI.io lists $0.15 per 1,000 tweets.
Weir reads public posts only, and it isn't licensed by X, so access can change.
FAQ
How do I find leads on Twitter?
Search X for a buying phrase plus your category, such as "alternative to" CRM, and exclude hiring, job and giveaway posts. Read each match on the Latest tab and reply by hand to the real buyers. A monitor can send you new matches daily.
Do you need a Twitter leads scraper?
Not to start. X's search box finds the same posts for free. A scraper or an API helps once you watch many categories or want alerts, and then personal data rules may apply to what you store.
Can I automate Twitter prospecting?
Automate the search and the alerts, and keep the contact human. X's developer guidelines allow automated replies only after a user engages first, and automated DMs only after they message you.
How many leads will one search find?
It depends on your category. Our CRM search found five matches in about a day, and one came from a likely buyer. A narrow category finds fewer posts, so watch several buying phrases at once.
Sources
All checked on 22 October 2026:
- X developer guidelines, automated actions: https://docs.x.com/developer-guidelines
- X search operators (quotes, OR, negation, lang:): https://docs.x.com/x-api/posts/search/integrate/operators
- X Developer Policy, storing X content: https://docs.x.com/developer-terms/policy
- European Commission, data protection explained: https://commission.europa.eu/law/law-topic/data-protection/data-protection-explained_en
- Slack incoming webhooks: https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks
- TwitterAPI.io pricing: https://twitterapi.io/pricing
- Weir searchX reference, monitors and billing: https://docs.weirapp.io/reference/x/searchX, https://docs.weirapp.io/monitors and https://docs.weirapp.io/billing
- Our two Weir searches for CRM buying intent, 22 October 2026: 10 credits