Quick overview
Audit recently updated HubSpot contacts before outreach. Find contacts with phone numbers, validate each number, skip unchanged records, and save available phone and messaging insights in HubSpot. The audit summary identifies contacts needing review. Start with free checks and add paid data when needed.
How it works
- Run manually for a rehearsal, or activate the included hourly schedule. Configuration defines the HubSpot portal, recent-update window, maximum batch size, selected checks, and spending maximum.
- Verify that the HubSpot credential belongs to the configured portal, then find recently updated contacts with a phone value. Oversized or incomplete search results stop before any lookup; they are never silently truncated.
- Process one contact at a time. Read the current phone and its actual property-history revision. Missing history, invalid numbers, and ambiguous inputs appear in the review output without purchasing a lookup.
- Use the verified QuietPass node to normalize and validate the number. Skip an unchanged phone when its matching HubSpot receipt was checked at or after that phone revision.
- For a fresh check, read the workspace controls and save the original operation before execution. Imports select only free basic details, with paid use disabled and a zero maximum. Optional paid checks require explicit configuration and authorized workspace limits.
- Read the retained result once. Settled results can continue to the CRM write; pending or expired results are retained for review. The workflow does not wait indefinitely or manufacture a replacement purchase.
- Read the contact again before writing. Check its current phone revision and number, then update only the 15 qp_phone_* properties. Preserve definite false answers and clear stale unknown fields. A final read and write are separate requests, so avoid overlapping audits.
- Produce an audit summary with updated, skipped, and review counts plus review contact IDs and available messaging indicators. Source phone, email, and consent fields are preserved. No calls, texts, or prospect messages are sent.
Setup
- In n8n Cloud, enable verified community nodes if needed and install QuietPass from the node panel. An instance owner or admin may need to do this. For self-hosted n8n, install the published n8n-nodes-quietpass version 0.1.2.
- Create your own QuietPass API credential and select it on both formatting nodes and every quietpass.com HTTP step. Complete account setup and credit activation first. For the free rehearsal, enable saved workflows at zero limits in QuietPass, leave credit authorization off, and keep the template’s free defaults. Never put a key into Configuration or workflow JSON.
- Create a HubSpot Service Key credential that permits account-details access and reading/updating contacts. Select the same credential on every HubSpot HTTP step. Create the 15 single-line text qp_phone_* properties listed at https://quietpass.com/integrations/n8n/ before running the audit.
- Set portalId, lookbackHours (24 by default), and maximumContacts (25 by default; at most 100). Leave windowEnd empty for rolling runs. Set defaultCountry only when national-format input needs it. Click Run audit now and inspect the summary and HubSpot fields before publishing or activating the hourly schedule.
Requirements
- A QuietPass account ready for API use; a HubSpot account with the required contact properties and Service Key permissions; and an n8n instance with the verified QuietPass node installed. The template is free; optional lookup data and n8n or HubSpot platform charges are separate.
Customization
- Choose a smaller lookback window or a batch limit up to 100. Use an explicit past ISO UTC windowEnd for a manual catch-up, then clear it before enabling the schedule. To add phone-network or messaging checks, review country coverage, enable paid use explicitly, and set workspace and per-lookup limits. When changing check selection, use skipExisting false for the reviewed run.
Additional info
Full setup and recovery guide: https://quietpass.com/integrations/n8n/
The separate recovery download reads an original saved result and retries the guarded CRM write without buying another lookup. Results are retained for 24 hours. Keep the original operation ID, contact ID, and phone-history revision from a failed execution.
SMS support may be inferred from mobile number type. App registration and number status do not establish consent, ownership, or guaranteed delivery.
The workflow passed nine fictional cases in the n8n 2.44.6 engine using the published 0.1.2 node, including mixed contacts, repeat runs, paused spending, changed source, pending results, and failed writes. These fixtures spent no supplier credit and do not claim live customer CRM access.