Skip to content

fix(briefs): replace dead LinkedIn Actor in intel scraper - #12

Open
johnisanerd wants to merge 4 commits into
SCTY-Inc:mainfrom
johnisanerd:fix/linkedin-intel-actor-404
Open

johnisanerd wants to merge 4 commits into
SCTY-Inc:mainfrom
johnisanerd:fix/linkedin-intel-actor-404

Conversation

@johnisanerd

Copy link
Copy Markdown

agentcy-briefs intel scrape fails for any brand with a LinkedIn handle, because anchor/linkedin-profile-scraper returns 404 on Apify.

_scrape_linkedin() now calls johnvc/linkedin-posts-api and maps its rows (one per post) to the same dict keys. I also pinned apify-client<3 in the intel extra: 3.x returns a model from call() instead of a dict, which breaks run["defaultDatasetId"] in all three scrapers, and a fresh install picks 3.3.0 today. I added a mocked test, and make check-python and make lint pass.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-24T22:04:05.995550Z 9e0a068 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant