Twitter Posts
A person's posts on Twitter.
This insight captures what a prospect is saying publicly on Twitter/X, helping you uncover personal beliefs, strategic focus areas, or signs of engagement that can be used to inform your outreach.
Why does this insight matter?
- Reveals the prospect’s voice and tone in their own words
- Surfaces active pain points, strategic initiatives, or industry views
- Allows reps to reference specific tweets as contextual hooks
- Provides an opportunity to align your value prop to their interests
- Can spark rapport with hard-to-reach personas
Insight Subtypes and Usage
- Subtype:
socialMediaProspectRecentTwitterPosts
API Controls
Generate Insights API
To generate this insight, you only need to provide the prospect’s email or LinkedIn profile URL. Autobound handles resolution of the correct Twitter handle automatically.
{
"insightSubtype": "socialMediaProspectRecentTwitterPosts",
"contactEmail": "[email protected]"
}
Only one of contactEmail or contactLinkedinUrl is required. If both are provided, resolution is more accurate.
Autobound uses proprietary resolution logic—including cached metadata, pattern matching, and third-party signals—to match the correct Twitter handle to the right prospect.
Generate Content API
To mandate this insight for content generation, include it in the list of enabled insights:
{
"enabledInsights": ["socialMediaProspectRecentTwitterPosts"]
}
Or to mandate Twitter Posts to be excluded from your output, turn off the insight from Insight Control, or add the following to your generate-content request:
{
"disabledInsights": ["socialMediaProspectRecentTwitterPosts"]
}
What the Output Includes
Each returned insight is an object containing a single variables
section, which includes all tweet and profile metadata needed for downstream workflows, automation, or UI display. Each tweet generates a separate variables object.
-
Profile and Tweet Metadata For each tweet, the
variables
object includes:userName
— The display name of the user who posted the tweetuserHandle
— The Twitter/X username (without the @ symbol)userBio
— The user’s Twitter/X biouserLocation
— The user’s location as listed on their profilefollowers
— The number of followers the user had at the time of retrievalfollowing
— The number of accounts the user was followingverified
— Whether the user’s account was verified at the time of retrievalpostDate
— The UTC date and time the tweet was posted (ISO8601 format)postType
— Always “Twitter” for this insight typelikes
— The number of likes on the tweetretweets
— The number of retweetsreplies
— The number of repliesviews
— The number of times the tweet was viewedlink
— The canonical URL to view the tweet on Twitter/XtweetId
— The unique identifier of the tweettweetText
— The full text content of the tweet
-
Engagement Summary Fields (per tweet) Each variables object also repeats summary fields for convenience:
totalTweets
— Total number of tweets in this insight runtotalViews
— Total views across all tweetstotalLikes
— Total likes across all tweetstotalRetweets
— Total retweets across all tweetstotalReplies
— Total replies across all tweets
Example Output Snippet
{
"variables": {
"userName": "Ethan Evans",
"userHandle": "EthanEvansVP",
"userBio": "Former Amazon VP...",
"userLocation": "Traveling the world",
"followers": 30217,
"following": 23,
"verified": true,
"postDate": "2025-06-09T21:51:14Z",
"postType": "Twitter",
"likes": 155,
"retweets": 10,
"replies": 1,
"views": 11029,
"link": "https://twitter.com/EthanEvansVP/status/1932193799314563265",
"tweetId": "1932193799314563265",
"tweetText": "This diagram explains how to build trust quickly and well...",
"totalTweets": 13,
"totalViews": 82439,
"totalLikes": 862,
"totalRetweets": 66,
"totalReplies": 36
}
}
Example Usage in Outreach
"Saw your tweet on building trust for executive promotion—loved the framework. That’s actually something we help leadership teams formalize and scale..."
Updated 17 days ago