Phone checks in your workflow.

Install and connect

Use the installation invitation to add QuietPass to your Make organization. This connector is shared by invitation; it is not a Marketplace listing.

Install QuietPass in Make ↗

1. Create your connection.

   In QuietPass, open API keys & usage and create a server API key. In Make, select a QuietPass module, add a connection, and enter that key in the password field. Each customer uses their own workspace and credit.

2. Keep credentials in connections.

   Never put an API key in a spreadsheet, CRM property, workflow note, or exported blueprint. Select your own HubSpot or Google connection after importing.

3. Rehearse before scheduling.

   Imports have no saved connections, a zero price ceiling, and credit use disabled. Keep the scenario inactive until you have configured it and completed one manual run.

Choose your workflow

In a new Make scenario, choose More → Import blueprint, select the downloaded JSON, choose your own connections, and save. Read the source-specific setup below before running.

Your limits. Your choice.

Start with a free complete workflow. Select only Number details in Prepare a saved phone check, keep its ceiling at 0, and leave Allow credit use set to No. In QuietPass, keep the per-lookup and daily limits at zero and enable future saved-operation lookups without authorizing credit use. Run the scenario manually on one number you own or have permission to check. Confirm that the result reaches your CRM or sheet, then pause again while you decide which paid checks to add.

A zero ceiling accepts only free basic checks. Selecting a paid check at zero returns AUTOMATION_OPERATION_CAP before an operation is saved. Choose a positive ceiling and the corresponding workspace limits when you are ready to use paid checks; keep the original source record and revision when retrying.

Open Connected tools → Workflow spending limits. Set the maximum per lookup and shared daily maximum in your workspace currency, authorize credit use, and enable future lookups. Every workspace starts paused at zero. A workflow key can read these limits; it cannot raise them or resume spending.

In the workflow’s Prepare a saved phone check step, choose checks and set Maximum per lookup. For example, 50000 means £0.05, US$0.05, or €0.05 in the workspace currency. In Run a saved phone check, set Allow credit use to Yes only when ready. The workflow ceiling cannot exceed the console ceiling.

Formatting and quotes are free. Phone services cost 0.02 and messaging apps cost 0.03 in your workspace currency. Selecting both costs 0.05 per number at current prices. Make may charge its own credits for modules separately.

Pause in QuietPass stops new purchases across these saved-operation workflows. A purchase already committed may finish; saved-result recovery remains available. Usage resets at midnight UTC, with pending reservations carried over. Direct API calls and the native HubSpot connection have their own controls.

Set up HubSpot CRM

Select your HubSpot connection on every HubSpot module. Replace REPLACE_HUBSPOT_PORTAL_ID in the prepare step’s Workflow ID with your portal ID. Keep that workflow namespace stable on retries. This template reads the contact’s phone and hs_country_region_code; national phone input needs a two-letter country code.

Create these contact properties in HubSpot Settings → Properties. Use single-line text, the exact internal names below, and labels of your choice. The workflow writes only these 15 properties; it does not change the source phone, email, consent, or marketing settings.

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

The contact ID and latest phone-property history timestamp identify each check. Writing a result does not create another paid check. Missing phone history or invalid input stops before purchase. Before updating, the workflow rereads the phone and its revision, and skips a result already written. A changed phone prevents an old result from being applied.

The final reread and update are separate HubSpot requests, so a very small edit window remains between them. The stored international number and checked-at timestamp show which phone the result describes. Definite false stays false; unknown values clear old QuietPass fields.

Set up Google Sheets

Create two tabs in your workbook, with these exact column headers in row 1:

PaidContacts, A:D

record_id, phone, country_code, source_revision

QuietPassResults, A:Q

record_id, source_revision, operation_id, request_id,
e164, country, line_type, carrier, sms, sms_basis,
whatsapp, telegram, reachable, checked_at, state,
charged_amount, currency

Replace REPLACE_SPREADSHEET_ID in the trigger and prepare step’s Workflow ID. Select your Google and QuietPass connections. Use a permanent, unique record ID and an explicit revision such as phone-1. Preserve both when retrying; never use row numbers, random values, NOW(), or Make execution IDs.

For a changed phone, append a new input row with the same record ID and a new revision. The trigger watches new rows, not arbitrary cell edits. Results are appended to a separate receipt ledger, so sorting input cannot attach a result to another contact. Invalid input or a failed free-format request is skipped before purchase and remains in Make execution history for review.

To display the current international number, match both record ID and source revision in a separate view. For a view with record ID in A2 and current revision in D2:

=IFERROR(LOOKUP(2,1/((QuietPassResults!A$2:A=A2)*(QuietPassResults!B$2:B=D2)),QuietPassResults!E$2:E),"")

Adapt formula separators to your spreadsheet locale. A lost append response can produce duplicate identical receipts on retry. Deduplicate by operation_id for reporting; replaying the same operation does not buy another lookup. Unknown fields stay blank, and definite false remains false.

Use an API endpoint directly

The Make an API call module uses your existing QuietPass connection. Enter a relative path such as /v1/coverage, choose a method, and add query parameters or a JSON body as needed. Authentication is added automatically; never paste a key into a module field.

Reads, free formatting, quotes, and saved-operation preparation work with credit permission off. Other writes require explicit permission. A direct lookup uses normal currency amounts and a stable Idempotency-Key. Quotes are optional. Use the saved-check modules above when you need shared daily workflow limits and retained-result recovery.

The destination is fixed to QuietPass and redirects are disabled. See the API guide and OpenAPI reference for supported endpoints.

Recover a failed destination write

Find the original operation ID in the saved Make execution or QuietPass’s recent operations. Import the recovery blueprint for your destination and select your connections. For CRM, enter the original operation ID, contact ID, and original phone revision wherever the placeholders appear. For Sheets, enter the original operation ID, record ID, revision, and workbook ID.

Recovery reads the original retained result and retries only the destination write. It cannot prepare or purchase a new lookup and works while purchases are paused. CRM recovery still checks the current phone and revision. Sheets recovery appends the original revision’s receipt.

Only a settled, retained result is written. Pending, expired, or unavailable is not a negative answer. Results are retained for 24 hours; review expired work before explicitly authorizing a new check. Never manufacture a new source revision automatically after an error.

Keep incomplete execution storage enabled and scenarios sequential. Make execution history can contain phone inputs and returned data; restrict access and configure retention. Review stopped filters and errors before replaying. For help, include the operation or request ID, not your API key.

API guide · OpenAPI reference · Get help