Connected tools
A clearer picture. In your CRM.
Connect HubSpot to QuietPass. Check new and changed contact phone numbers, then save the results alongside the contact.
See phone details in a CRM workflow
51 seconds · Silent, captioned walkthrough using fictional test records and edited QA screenshots. The CRM video shows separate Make and HubSpot examples, rather than one continuous run.
Keep phone intelligence beside the contact, ready for the next workflow step.
Connect HubSpot See lookup pricing
Direct OAuth installation; not Marketplace listed.
Before you connect
You need a QuietPass account with an active balance in GBP, USD, or EUR, and workspace-owner access. In HubSpot, use a Super Admin or a user authorized to install apps and grant the requested contact and property permissions. Contact us if HubSpot does not appear in your QuietPass console.
QuietPass reads contact phone numbers and creates and updates its own phone-intelligence properties. It requests contact read/write and contact-property read/write access. It does not request company, deal, email, marketing-subscription, or consent permissions. No QuietPass API key is needed for this native connection.
Direct installation. HubSpot may display an unverified or unreviewed-app warning during installation. This app does not have HubSpot Marketplace approval. Check that the app is QuietPass, the return address is on quietpass.com, and the permissions match this guide before you decide to connect.
Connect your account
- Sign in to QuietPass and open Connected tools.
- In the HubSpot section, select Connect HubSpot.
- Sign in to HubSpot, choose the account you want to enrich, and review the permissions. Complete HubSpot's confirmation only if you approve.
- When you return to QuietPass, check the connected HubSpot account ID. Automatic checks start paused.
- Select Create QuietPass contact fields if prompted. This creates the dedicated properties; it does not run phone lookups. If conflicting properties already exist, QuietPass stops for review instead of replacing them.
One HubSpot account can be connected to one active QuietPass workspace. Reconnect uses that same account; switching to a different HubSpot account is not supported.
Choose checks and spending limits
Use Checks and spending limits in the HubSpot section. These controls are separate from the shared Make and n8n workflow limits above them.
- Select the data you want. Number details is free. Phone checks and messaging-app checks use the package prices shown in QuietPass pricing: 0.02 and 0.03 respectively in your workspace's fixed currency. Selecting multiple checks from one package buys that package once per lookup.
- If this CRM consistently uses national-format numbers from one country, select that default country. Otherwise, leave No default — require international format. A country is needed to interpret a local number correctly.
- Set Maximum per contact and Maximum per day in your workspace currency. For example, 0.05 allows both packages for one contact. A 1.00 daily ceiling allows at most twenty such 0.05 lookups.
- Check Enable automatic checks for future contact events and select Save settings when you are ready. This authorizes use of your existing trial or purchased credit within those limits.
For a free first test, select only Number details, keep both limits at zero, and enable checks. For paid checks, both a sufficient balance and sufficient limits are required. The daily limit resets at midnight UTC; pending reservations still count. Limits do not create a subscription, a card charge, or automatic top-ups.
Receive contact updates
After you enable checks, a newly created contact or a change to its Phone Number property schedules work. QuietPass processes updates about every five minutes. Follow progress under Recent contact updates in QuietPass. Higher volume or supplier delays can take longer.
Existing contacts are not scanned when you connect. To start with one authorized contact, add or update its phone number after you enable checks. Changes to QuietPass result properties do not trigger another lookup. Repeated events for an unchanged normalized number are skipped without another purchase.
QuietPass rereads the current source number before writing a result. Only the qp_phone_ fields are updated; the source phone, email, and consent fields stay unchanged. The source reread and CRM write are separate requests, so the stored number and checked-at time identify the number that was checked if a concurrent edit occurs.
Understand your QuietPass fields
In HubSpot, open a contact's properties and find the QuietPass phone intelligence group. Add the properties you need to your contact view or reports.
| Contact information | Properties |
|---|---|
| Number | qp_phone_e164, qp_phone_country, qp_phone_valid, qp_phone_type |
| Network | qp_phone_carrier, qp_phone_ported, qp_phone_reachable |
| Contact options | qp_phone_sms, qp_phone_sms_basis, qp_phone_whatsapp, qp_phone_telegram |
| Result receipt | qp_phone_status, qp_phone_reason, qp_phone_checked_at, qp_phone_request_id |
These properties are text fields. true and false are definite answers; blank means unknown or not included, rather than false. Each successful write replaces the whole QuietPass field set so an old value does not look current.
SMS support inferred from mobile line type is labeled mobile_line_type. Direct landline enablement checks are limited to supported US/Canada numbers. SMS support does not guarantee delivery. WhatsApp and Telegram indicate reported account registration; network reachability is a separate observation. Coverage and available answers vary by country and network.
Resolve an issue
Start with Recent contact updates and Refresh status. A missing or ambiguous country, invalid number, insufficient balance, spending cap, or disconnected account can stop an update. Fix the underlying issue before retrying. If the original request or result is still retained, Retry saved work schedules another attempt using that saved work; it does not create a replacement purchase.
If HubSpot is temporarily unavailable after a lookup finishes, QuietPass retains the result before retrying its CRM write. Retries are bounded. Saved result snapshots are retained for 24 hours; an expired result needs review rather than an automatic fresh purchase. The native connector must be enabled for a saved CRM write to resume.
For an authorization issue, select Reconnect and approve the same HubSpot account again. If HubSpot's browser check fails, try a private browser window. Don't repeatedly create new lookups to work around an uncertain result. Send hello@quietpass.com the request reference and issue description; keep credentials and customer phone data out of email.
Pause, disconnect, or uninstall
Pause checks stops new native contact processing. Work already sent to a supplier may finish and settle its charge. Native saved CRM writes wait until checks are enabled again. Your configured limits remain available to edit; set them to zero as well if you want a zero-spend configuration.
Disconnect turns processing off, removes QuietPass's stored authorization, and attempts to revoke HubSpot access. If QuietPass cannot confirm revocation, remove the app from HubSpot too. You can also uninstall it in HubSpot under Settings → Integrations → Connected Apps → QuietPass, using the available uninstall action. Review HubSpot's confirmation before continuing.
Disconnecting or uninstalling does not delete your contact records, source values, or the QuietPass properties and results already written in HubSpot. Those remain under your HubSpot retention settings and can be removed there if desired. Pending connector snapshots are cleared on disconnect; financial records and already-dispatched charges follow QuietPass's normal billing and retention rules. See data handling, Privacy, and Terms.