Skip to main content
Web Extraction

Bluesky Post Finder

Fetch one public Bluesky post from a canonical bsky.app URL, including author details, engagement, embeds, media links, and nested replies when available.

View details

Inputs

Loading input fields...
Execution Steps

Loading workflow structure...

Loading curated examples...

Overview

Bluesky Post Finder fetches one public Bluesky post from a canonical bsky.app post URL, including author details, text, engagement, embeds, media, links, and nested replies when returned. Use it to inspect a specific post's context before quoting, summarizing, or building social-listening notes.

Use cases

  • Capture a specific Bluesky post's text, author, media, links, and engagement before referencing it.
  • Inspect returned reply threads to understand early audience reaction and follow-up context.
  • Turn a Bluesky post URL into structured data for reports, briefs, or comparison notes.

Input tips

  • Paste a canonical HTTPS Bluesky post URL from bsky.app.
  • Use Bluesky User Activity Feed when you need to discover candidate posts first.
  • Use Bluesky Profile Finder for account context before or after inspecting the post.

Expected output

The AI Tool returns lookup status, requested and canonical URL, warnings, normalization notes, additional recovered fields, cost metadata, an optional normalized post, reply threads, and replyThreadCount. The post can include URI, content ID, public URL, text, timestamps, language tags, labels, links, mentions, tags, author details, author relation, engagement counts, external link cards, media assets, reply context, thread controls, and per-post recovered fields. Replies can include top-level reply posts and one additional nested reply level when returned.

Caveats

  • Only public post data returned by the source is included.
  • Replies can be partial; absence of replies does not prove the post has no conversation.
  • Engagement counts, labels, media links, and reply visibility can change after the run.
  • The input must be a canonical bsky.app post URL, not a profile URL or search query.