Skip to content

Actions: brightdata/linkedin-scraper-node

Actions

Live check

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
live.yml
24 workflow runs
24 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Daily check: is anything broken? Live check #24: Scheduled
1m 14s main
main
1m 14s
Daily check: is anything broken? Live check #23: Scheduled
1m 14s main
main
1m 14s
Daily check: is anything broken? Live check #22: Scheduled
1m 21s main
main
1m 21s
Push check: Trim the contributing guide Live check #21: Commit 6d6c437 pushed by anil-bd
49s main
main
49s
Push check: Add a short contributing guide Live check #20: Commit ca0994e pushed by anil-bd
51s main
main
51s
Push check: Drop the note about the repository being private Live check #19: Commit e16694d pushed by anil-bd
41s main
main
41s
Push check: Update the banner to the design team's version Live check #18: Commit cac8650 pushed by anil-bd
1m 38s main
main
1m 38s
Push check: Update the banner to the design team's version Live check #17: Commit cac8650 pushed by anil-bd
3s main
main
3s
Daily check: is anything broken? Live check #16: Scheduled
1m 38s main
main
1m 38s
Daily check: is anything broken? Live check #15: Scheduled
56s main
main
56s
Weekly check: does every README block still work? Live check #14: Scheduled
2m 39s main
main
2m 39s
Push check: Stagger the scheduled runs so the scraper repos never overlap Every scraper repo ran its daily and Monday checks at 06:00 UTC. On Monday that is the full README matrix in all four at once, up to about sixteen jobs against one account, which is the burst that returned "Your system is sending too many of this type of request" during the LinkedIn Python build. Valid inputs fail with that error, so the runs would go red with nothing wrong in the code. The Monday runs now start at 06:00, 06:20, ... Live check #13: Commit ab35362 pushed by anil-bd
40s main
main
40s
Push check: Describe this workflow, not the Instagram one it was ported from The header block and the scrape job's name still said "one post from nasa" and "Fetch the posts", inherited from the Instagram twin. Both are the first thing a maintainer reads, and in this repository they named the wrong thing entirely. No behaviour changes. Live check #12: Commit 0bb2403 pushed by anil-bd
51s main
main
51s
Push check: Add the LinkedIn banner 2400x520, the LinkedIn twin of the Instagram one. The endpoint row and the subtitle are claims, and both hold: /profiles, /companies, /jobs and /posts are all in the endpoint table, collect takes URLs, and discover takes a name or a keyword. The README line was parked in a comment so the repository front page would not show a broken image before the file existed. Restored now. Live check #11: Commit f3d78b9 pushed by anil-bd
1m 1s main
main
1m 1s
Daily check: is anything broken? Live check #10: Scheduled
1m 18s main
main
1m 18s
Daily check: is anything broken? Live check #9: Scheduled
1m 14s main
main
1m 14s
Push check: Badge job: start from the tip of main, so a re-run cannot conflict The daily run on 2026-09-18 failed with a merge conflict in README.md. Attempt 1 of that run failed its scrape job, so the badge job wrote "last check failed" and pushed it. Attempt 2, a re-run three hours later, passed and wrote "last verified". But a re-run checks out the commit the run first started on, not the current tip. So attempt 2 edited the badge line from a base that did not have attempt 1's edit to the same line,... Live check #8: Commit b35c7af pushed by anil-bd
44s main
main
44s
Daily check: is anything broken? Live check #7: Scheduled
1m 6s main
main
1m 6s
Daily check: is anything broken? Live check #6: Scheduled
1m 32s main
main
1m 32s
Scrape satyanadella Live check #5: Manually run by anil-bd
1m 1s main
main
1m 1s
Push check: Name the CLI pipeline that exists, and keep the pii flag in the field table Two fixes the live run surfaced. The coding-agents block called bdata pipelines linkedin_profiles, which is not a pipeline. I wrote it by analogy with instagram_posts instead of running bdata pipelines list. The real name is linkedin_person_profile. The README now names the five LinkedIn pipelines the CLI actually has. The daily field-table generator rewrote the table and dropped two things it should have kept:... Live check #4: Commit 917fd35 pushed by anil-bd
40s main
main
40s
Scrape satyanadella Live check #3: Manually run by anil-bd
3m 4s main
main
3m 4s
Push check: Point the compliance line at a URL that exists The live check's link step caught it: brightdata.com/legal/compliance is a 404. I wrote that path from assumption instead of verifying it. The LinkedIn product page links compliance to brightdata.com/legal-governance, which returns 200. Use that. This is what the link step is for. It ran before any credit was spent, because it sits ahead of the fetch step in the same job. Live check #2: Commit e128327 pushed by anil-bd
32s main
main
32s
Push check: The JavaScript LinkedIn twin of instagram-scraper-node LinkedIn profiles, companies, jobs and posts as JSON, on the Bright Data LinkedIn Scraper API, through @brightdata/sdk 1.2.0. Every README code block was run against the live API and shows its real output. The sample file comes from a real run of the CLI. Examples use public figures and company pages, never a private individual. Shape differences from the Instagram twin, all documented in the README: - Every profile asked for goes in ... Live check #1: Commit 23902e1 pushed by anil-bd
43s main
main
43s