A static account list gets old quickly. Companies launch products, hire specialists, compare tools, and describe new problems in public.
This workflow adds directional intent data to account-based marketing research without treating every mention as a sign that someone is ready to buy.
SocialListeningAPI searches public posts on LinkedIn, X, and Reddit and Google results for the phrases you choose. It returns normalized records with source URLs.
Step 1: Define the accounts and events
Create a SocialListeningAPI account and claim the 100 free credits. Choose a small target account list, then define events that could change your research.
Useful event groups include:
- Product launch:
Acme launchedorAcme introducing - Hiring:
Acme hiring data engineer - Tool research:
Acme alternative to competitor - Problem post:
Acme struggling with data quality - Leadership post:
founder name customer research
Use company and product names exactly as customers write them.
Step 2: Search for current intent data
Run each query across LinkedIn, X, Reddit, and Google:
for endpoint in \
linkedin/search-posts \
x/search-posts \
reddit/search-posts \
google/search
do
curl --get "https://api.sociallisteningapi.com/api/v1/$endpoint" \
--data-urlencode 'query=Acme hiring data engineer' \
--header 'x-api-key: YOUR_API_KEY'
doneLinkedIn search costs 2 credits, and each other search costs 1 credit. One query across all four sources costs 5 credits. The API documentation explains the shared response shape. If you prefer an agent workflow, connect the MCP to Claude or ChatGPT.
Step 3: Store each account event
Save the account, event type, source URL, published date, query, and a short evidence note in an external database. Use the URL as the duplicate key.
SocialListeningAPI returns public search records. Your database handles history and deduplication.
Step 4: Score evidence outside the API
Compare each event with the account plan. A direct tool question may deserve more attention than a generic company mention. Keep the original source beside every score so a person can check it.
An external LLM can label event types, but it should not decide that an account is ready to buy.
Step 5: Review the weekly feed
Send new, relevant events to the account owner once per week. Research the source before changing outreach or messaging. Scheduling, scoring, CRM updates, and alerts all happen outside SocialListeningAPI.
Conclusion
Choose ten accounts and two event types for the first run. Wider coverage can wait until those signals change a real research or outreach decision.
A useful feed explains what happened, when it happened, and where the evidence came from. It does not label ordinary activity as intent.
Continue with Build a Startup Funding Trigger List.
