Phone intelligence for your Clay tables.

Connect your workspace

This setup uses Clay’s standard HTTP API action. The download is a request recipe to configure manually, not a native Clay app or an importable workbook.

Download HTTP recipe Fictional test rows

1. Keep the table manual.

   Turn off table Auto-run, each HTTP column’s Auto-run, and any schedules. Rehearse with fictional data before adding customers.

2. Preserve the phone text.

   Use a Text column for phone numbers. CSV imports can be inferred as Number and lose a + or a leading zero. Check the imported values against your source and restore any removed characters before running. Keep a permanent record ID, an explicit phone revision, and a two-letter country code for national input.

3. Save your connection.

   Create a server API key in QuietPass → API keys & usage. In Clay, add HTTP API → Configure → Add account. In the saved HTTP API (Headers) account, set Key to Authorization and Value to Bearer YOUR_QUIETPASS_SERVER_KEY. Each customer uses their own key and credit. Keep keys out of table data, formulas, notes, exports, and support messages.

Start with free formatting

Use POST to https://quietpass.com/v1/phone/check. Insert the phone and country columns with Clay’s / picker inside this JSON body; replace the descriptive placeholders with real column tokens.

{
  "phone": "<phone column>",
  "default_country": "<country column>",
  "checks": ["basic_line_type"]
}

Keep Follow redirects, Retry on failure, and Auto-run off. Save without running, then manually run one fictional row. International + or 00 input can omit the country; national input needs its ISO country, such as GB or US.

Valid formatting returns number.e164, number.country, and number.valid. Invalid input returns HTTP 400 with error.code=INVALID_PHONE_NUMBER. Stop on a non-2xx response; retain its request ID and do not continue to paid checks. Formatting does not establish assignment, ownership, reachability, or delivery.

Choose which rows can use credit

Use the saved-operation requests in the recipe for paid checks. First open QuietPass → Connected tools → Workflow spending limits, set a per-lookup and shared daily maximum, authorize credit use, and enable future saved lookups. New workspaces start paused at zero. An API key cannot raise limits or enable spending.

1. Read the limits.

   GET /v1/automation/settings. Require available=true and enabled=true, and use the workspace’s exact GBP, USD, or EUR currency.

2. Prepare the row.

   POST /v1/automation/operations. Use a fixed workflow namespace containing your Clay workspace and table IDs, the permanent record ID, and an explicit phone-source revision. Keep each identity component at most 128 characters. Preserve these on retries; never use a row position, current time, run ID, or result-update timestamp. Save the returned operation id immediately.

3. Run that operation.

   POST to /v1/automation/operations/<original-id>/run. The recipe starts with maximumMicros=0 and allowPaid=false. Set a deliberate integer cap and allowPaid=true only after authorization. Keep this column manual and add a run condition requiring the row’s explicit approval. Compare text values to "true" explicitly; the text "false" must not grant permission.

50000 means 0.05 in your fixed workspace currency. Current package prices are 0.02 for phone checks and 0.03 for messaging apps; both together cost at most 0.05 per number. Workspace caps and balance still apply. Clay action executions are charged separately under your Clay plan.

Recover the original result

GET /v1/automation/operations/<original-id>. This only reads and reconciles the saved operation; it cannot purchase another lookup. Continue only when state=settled, resultState=settled, and result.requestId exists.

If execution loses its response or a destination write fails, recover using the original operation ID. Never create a replacement operation for uncertain work. If preparation alone loses its response before you know the ID, repeat only the exact original identity, phone, checks, and limits. Pending and expired states stop downstream writes. Results are retained for 24 hours; expired work needs review before a deliberately new event is authorized.

Write results without changing the source

The recipe’s resultPaths maps formatted number, carrier, line type, SMS support and basis, WhatsApp and Telegram registration, and network reachability. Write these into dedicated result columns. Preserve false as a definite negative and null as unknown. Messaging registration does not establish consent.

Before writing or exporting, confirm the phone and source revision still match the saved operation. Leave the source phone and consent fields unchanged. Keep the operation ID, result request ID, and checked time alongside the result so you can recover without another purchase.

QuietPass’s pause stops new saved-operation purchases across this workspace, including Make and n8n workflows. Already dispatched requests may finish; retained results remain readable. Direct API actions and the native HubSpot connection have separate controls.

Clay HTTP API instructions ↗ · QuietPass API guide