X Post Read
Read and summarize a public X or Twitter post with a compact Markdown result.
What it does
Reading X/Twitter posts programmatically requires the official API with rate limits, OAuth tokens, and JSON parsing. This connector takes a single post URL and returns the author, post date, and a structured summary — formatted as Markdown, ready for your agent workflow.
Inputs
| Parameter | Format | Example | Required |
|---|---|---|---|
url | string | https://x.com/verabornyakov/status/1234567890 | Yes |
Outputs
| Field | Type | Description |
|---|---|---|
author | string | The handle and display name of the post author |
postedAt | string | When the post was published (ISO 8601) |
summary | string | A structured summary of the post content |
Example output
Input
url: "https://x.com/verabornyakov/status/1234567890"
Output
# X Post Read - Author: @verabornyakov - Posted: 2026-03-08T14:22:00Z - Summary: The author discusses three underrated SEO strategies for SaaS companies: programmatic content clusters, internal link optimization, and leveraging changelog pages for organic traffic.
What it means
The post is a thread starter about SaaS SEO tactics. The summary captures the main points without needing to visit X directly.
Last tested: 2026-03-10
How to install
Via CLI
Via web
- Visit the connector catalog and find X Post Read.
- Click Install connector and acknowledge any training requirements.
- Complete authorization if prompted.
- Use the connector from Chat or the CLI.
Auth and permissions
| OAuth required | No |
| Managed auth | Included, no API key needed |
| Bring your own key (BYOK) | Not supported in v1 |
| Audit logged | Every request is logged with input, result, cost, and timestamps |
| Training acknowledgment | Not required |
Admins can restrict this connector via blacklist or whitelist in the admin panel.
Limits and edge cases
- •Only public posts are supported. Protected or private accounts will return an error.
- •The URL must be a direct link to a single post (e.g., https://x.com/user/status/123).
- •Thread reading is not supported — only the initial post is returned. Use X Post Replies Read for thread context.
- •Posts that have been deleted or suspended will return a "not found" error.
- •Media attachments (images, videos) are not extracted — only text content.
Common use cases
Summarize an X thread for a newsletter digest
Feed the post URL and get a structured summary you can paste into a newsletter.
Monitor competitor announcements on X
Automate daily reads of key posts from competitor accounts.
Extract quotes and insights for content creation
Read multiple posts and compile talking points for a blog article.
Frequently asked questions
Can I read private or protected posts?
No. Only publicly visible posts are supported.
Does this read the full thread?
No. It reads a single post. For replies, use the X Post Replies Read connector.
What URL formats are accepted?
Standard X/Twitter post URLs: https://x.com/user/status/123 or https://twitter.com/user/status/123.
Is there a rate limit?
High-volume usage can hit temporary throttling. Vernclaw retries when possible and otherwise returns an error.
Related connectors
X Post Replies Read
Read public replies for a referenced X post.
X Article Read
Read public X article pages with normalized title, author, and excerpt output.
X Search
Run advanced X search queries and normalize the top matching public posts.