n8n Workflow: Check Searchbug Reassigned Numbers to Google Sheets

Automatically check whether submitted phone numbers are reassigned—and log the result to Google Sheets

This n8n workflow takes a phone number and a consent/contact reference date from an n8n form, queries Searchbug’s Reassigned Numbers Database (api_rnd) for reassignment status, then appends both the raw outcome and a plain-English interpretation to Google Sheets.

What this workflow does

• Receives form submissions from an n8n form containing a phone number and a consent/contact reference date.
• Cleans and normalizes inputs: strips the phone number down to digits only and formats the date as YYYY-MM-DD.
• Calls Searchbug api_rnd using an HTTP POST request with the cleaned phone number and reference date.
• Interprets the API response: extracts the reassigned status (YES/NO/NO_DATA/ERROR) and adds a human-readable meaning.
• Logs everything to Google Sheets by appending a new row, including submitted/cleaned values, API fields, raw response, and a created timestamp.

Use cases

• Quality checks for SaaS or compliance workflows that need to validate whether a phone number has been reassigned.
• Operational tracking: keep an audit trail of API results (status, raw API response, and timestamps) for each submission.
• Workflow automation for customer onboarding or consent capture, where you must record the reassigned-number outcome tied to a consent/contact date.

Technical details

• Nodes / tools: set, sticky note, form trigger, HTTP request, Google Sheets
• Searchbug integration: HTTP POST to the Reassigned Numbers Database endpoint (api_rnd) using headers CO_CODE and PASS
• Google Sheets: append-row step to a target spreadsheet/worksheet with headers such as Submitted Phone, Cleaned Phone, Consent Date, Reassigned Status, API Phone, API Date, Status Meaning, Raw API Response, and Created At

Setup tip: Create a sheet tab (e.g., “Reassigned Numbers”) with the required headers, then configure your Searchbug credentials in the HTTP request step.