Phone intelligence. Saved safely.

Install the QuietPass node

QuietPass is available as a verified node in n8n Cloud and compatible self-hosted n8n instances. In the workflow canvas, open the nodes panel, search for QuietPass, select it under More from the community, and choose Install. Installation requires an n8n instance owner or admin.

If QuietPass does not appear in n8n Cloud, ask the instance owner to check Verified community nodes in Instance settings. For self-hosted n8n, you can also install n8n-nodes-quietpass through Settings → Community nodes. Version 0.1.2 is the current verified release. n8n installation instructions.

Create a server API key for n8n, then add a QuietPass API credential. Keep credentials in n8n’s credential store, never in a Code node, Configuration, or workflow JSON. The examples use the QuietPass node for free formatting and built-in HTTP Request nodes for saved operations.

Download your workflows

• Recent-contact phone audit — find recently changed HubSpot contacts, check each phone separately, skip unchanged results, update QuietPass fields, and summarize records needing review.
• Single-contact checks — test an individual contact or adapt a trusted upstream contact event.
• HubSpot write recovery — retrieve the original result and retry a write without preparing or purchasing another lookup.

Use Import from File in n8n. The files contain no credentials or personal data. All import inactive. The audit includes a manual test and an hourly schedule that runs only after you publish or activate it. The other two workflows remain manual. n8n may select existing credentials during import; review every selected connection before execution. Paid use starts off with a zero spending ceiling.

Check recent contacts before outreach

For CRM and marketing-operations teams, the audit picks up recently updated HubSpot contacts that have a phone number. It checks the real phone history, rejects invalid input before buying checks, and writes the available phone and messaging results to the contact. The final Audit summary reports updated contacts, unchanged records skipped, and contact IDs needing review. It does not send messages or change source phone, email, or consent fields.

In Configuration, enter your HubSpot portal ID, choose lookbackHours (default 24, maximum 168), and review maximumContacts (default 25, maximum 100). The search includes all contacts modified during that window that have a phone value; unrelated CRM edits can also match. If there are more matches than the batch limit or the page is incomplete, it stops before any QuietPass lookup. Narrow the window or set windowEnd to an earlier ISO UTC time (for example 2026-11-01T12:00:00Z) for a bounded manual catch-up. Use successive non-overlapping windows for larger audits. Leave windowEnd empty for rolling runs and clear any fixed value before activating the schedule. This is a bounded audit, not an unlimited backfill or a durable change feed; after a gap longer than the window, review missed records explicitly.

For the first run, leave checks: ["basic_line_type"], allowPaid: false, and maximumMicros: 0. Enable saved workflows at zero limits in QuietPass, select credentials, then click Run audit now. This writes only the free result; network status and messaging registration require the relevant optional checks. Inspect the summary and CRM fields before activating the hourly schedule. The schedule uses UTC; adjust its timing in n8n if needed.

Overlapping runs skip an unchanged phone when its matching CRM receipt was checked at or after the latest phone-history timestamp. If you change which checks run, set skipExisting: false for the reviewed run: the CRM receipt does not store the original check selection. The saved-operation identity includes the selected check set and real phone revision; replaying it reuses the original operation. Concurrent runs can still race at the final CRM write, so avoid overlapping executions. HTTP failures stop the audit rather than silently dropping a record.

WhatsApp and Telegram registration identify contact options, not consent or guaranteed delivery. SMS support may be assumed from mobile line type. Use the separate SMS basis field and preserve unknown results when deciding the next step in your own workflow.

Connect your HubSpot portal

Select your own HubSpot Service Key credential in the CRM HTTP steps. It needs contact read/write access. The workflow verifies its actual portal ID before reading the selected contact. It does not use QuietPass’s internal CRM or require the native HubSpot connector.

Create a property group with internal name quietpass_phone and the following single-line text properties. Use these exact internal names. Only QuietPass properties are written; the source phone, email, and consent fields are preserved.

qp_phone_e164       qp_phone_country     qp_phone_valid
qp_phone_type       qp_phone_carrier     qp_phone_ported
qp_phone_sms        qp_phone_sms_basis   qp_phone_whatsapp
qp_phone_telegram   qp_phone_reachable   qp_phone_status
qp_phone_reason     qp_phone_checked_at  qp_phone_request_id

For each HTTP Request step calling quietpass.com, select your QuietPass API predefined credential. For each CRM step, select the same HubSpot Service Key credential. Keep redirects disabled.

Enable only the spending you choose

Open Connected tools → Workflow spending limits. New workspaces start paused at zero. Set your per-lookup and daily ceilings, explicitly authorize credit use, and enable future saved-operation lookups. These limits are shared with Make and Clay saved-operation workflows. Your workspace currency stays fixed; the workflow reads it automatically.

In the single-contact workflow’s Configuration, replace both IDs and set a country only when national-format phone input needs it. To rehearse at no charge, select only basic_line_type, leave allowPaid: false and maximumMicros: 0, and enable zero-limit workflows in QuietPass. For paid checks, review your limits and then explicitly set allowPaid: true with the chosen maximum. 50000 means £0.05, US$0.05, or €0.05 in the workspace currency.

Pausing prevents new purchases. An already-dispatched purchase may finish, and retained results remain readable. Workflow API keys cannot raise limits or resume purchases. Direct API calls and the native HubSpot connector have separate controls.

Use the single-contact alternative

The separate single-contact download starts with a manual contact ID. Execute it with an authorized contact. The workflow checks phone history and free formatting before preparing a paid operation. Invalid input, missing history, paused spending, or disabled paid use produces a review output. Uncertain requests stop and remain in n8n’s error history; they are not automatically retried as new purchases.

After the manual rehearsal, replace the manual input with a trusted upstream HubSpot contact-change event. Run one contact per execution and set its immutable contact ID. There is no automatic backfill or public webhook. The workflow reads the current phone and uses its latest property-history timestamp as the source revision. Never use the current time, an execution ID, or a random revision.

The operation ID and original quote are stored by QuietPass before execution. Replaying the same contact and phone revision reuses that operation. Before writing, the workflow reads the current phone again and checks its revision and saved request ID. A changed phone is not overwritten; a result already applied is skipped.

Definite false stays false. Unknown values clear old QuietPass fields. Pending or expired is not a negative answer. The final read and PATCH are separate requests, leaving a small window for a concurrent edit. The stored number, checked-at timestamp, and execution receipt identify which source was checked.

Recover a failed CRM write

Keep the failed n8n execution. Copy the original operation ID from Prepare saved operation, plus the contact ID and original phone-history revision from Source identity. Enter them in the recovery workflow’s Configuration and select your credentials.

Recovery performs only a retained-result read, free formatting, and a guarded CRM write. It has no prepare, run, quote, or purchase step and works while purchases are paused. Results are retained for 24 hours. If the result is pending or expired, or the source changed, it stops for review. Do not manufacture another revision to bypass an error.

A new run of a failed raw PATCH alone would skip source checks. Use the recovery workflow instead. Restrict n8n execution access and configure retention, because saved errors and manual executions can contain phone numbers and results. The template disables saving successful automatic executions and leaves error/manual execution history available for recovery.

API guide · Make workflows · Get help