Skip to content

Actions: brightdata/linkedin-scraper-node

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
36 workflow runs
36 workflow runs

Filter by Workflow

⌥ + click/return to exclude

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
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
Name the CLI pipeline that exists, and keep the pii flag in the field… Tests (automatic, no API calls, free) #3: Commit 917fd35 pushed by anil-bd
20s main
main
20s
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
Point the compliance line at a URL that exists Tests (automatic, no API calls, free) #2: Commit e128327 pushed by anil-bd
22s main
main
22s
The JavaScript LinkedIn twin of instagram-scraper-node Tests (automatic, no API calls, free) #1: Commit 23902e1 pushed by anil-bd
20s main
main
20s
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