n8n Scrape NSR Specialist Data to Google Sheets (Pagination)

Scrape Malaysia NSR Specialist Data with Pagination—Auto-load into Google Sheets

This n8n workflow manually scrapes Malaysia’s National Specialist Register (nsr.org.my) for a configured specialty (e.g., Cardiology), paginates through all results, enriches each doctor from their detail page, and appends or updates structured records in Google Sheets using the NSR License (NSR number) as the matching key.

What this workflow does

• Starts on manual run (you trigger it in n8n).
• Creates a session and performs the specialty search on nsr.org.my by requesting a session cookie and submitting the configured specialty search (configured for Cardiology via code 302).
• Paginates through every results page: parses the HTML table and accumulates each doctor’s NSR number, name, gender, and account ID.
• Enriches doctor records: after the last page, it loops through the full doctor list and opens each doctor’s detail page on nsr.org.my.
• Extracts graduation year and splits specialty: pulls the graduation year from the Basic Degree section and splits the listed specialty field into Specialty 1 and Specialty 2.
• Rate-limits requests using a brief wait to reduce the chance of throttling.
• Writes to Google Sheets: appends or updates rows in your sheet, matching by License (NSR number).

Use cases

• Maintain an up-to-date directory of specialist doctors for a specific specialty (e.g., Cardiology) in Google Sheets.
• Support internal research or lead lists by automatically enriching doctor details from NSR detail pages.
• Continuously refresh structured datasets in SaaS ops or analytics workflows using n8n + Google Sheets.

Technical details (n8n)

• Nodes/logic: if, code, wait, sticky note, http request, google sheets
• Google Sheets integration: uses an OAuth2 connection, writes to a specified spreadsheet tab, and updates by License (NSR number).
• Required sheet columns: Name, License, Specialty 1, Specialty 2, Gender, Grad Year.

Optional customization: to scrape a different specialty, update allSpecialty_ForSearch in the NSR search request and adjust the specialty label used during parsing if you rely on it downstream.