Create the properties in HubSpot
In HubSpot's property settings, create a contact property group named ScoreMachine. Add these six properties to the group.
Integrations · Zapier
Build a Zap that checks the phone number on every new HubSpot contact. Carrier, line type and ported status land on the contact.
Your first $5 of validations are on us, valid for 30 days. No card required.
score.phone.validation.mnpWebhooks by ZapierHubSpot
What you'll build
One run per new contact. Five results and the time of the check land on the contact.
A ScoreMachine account. Create your workspace with Start free. Your first $5 of validations are on us, valid for 30 days. No card required.
A long-lived API key. Ask your account manager for one. The key goes in the Token header of every request, where a login token would go. No key yet? The If You Have No API Key section logs in with your email and password.
Zapier Professional or higher. Webhooks by Zapier runs on the Professional, Team and Enterprise plans. The Free plan does not include it.
Permission to create HubSpot properties. Step 01 adds six properties to the contact record.
Six steps. The Zap runs every time HubSpot creates a contact.
In HubSpot's property settings, create a contact property group named ScoreMachine. Add these six properties to the group.
Create a Zap and pick HubSpot as the trigger. Connect your HubSpot account, then test the trigger.
The test pulls a recent contact. Its Phone Number field holds the number to check.
Add an action step with Webhooks by Zapier and pick Custom Request. Custom Request sends the Data field exactly as you enter it.
Replace PHONE with the Phone Number field from step 1. Keep the quotes on both sides of the field.
phones takes numbers in E.164 format, such as +447911123456. geo_iso_code is optional and takes a two-letter ISO country code.
The test output holds result, with phone_validation_mnp inside it.
Add Filter by Zapier. A failed call returns error in place of result. The filter stops the Zap before it writes to HubSpot.
Add a HubSpot action with the Update Contact event. Pick the contact from step 1, then map each property.
Zapier names each field after its path in the response. Pick the field whose path is shown above.
{{zap_meta_human_now}} is Zapier's built-in value for the time the Zap runs.
Test the HubSpot step, then open the contact in HubSpot. When the six properties hold values, publish the Zap.
Line type mobile · Carrier Vodafone · Ported true · Phone E.164 +447911123456
Six fields land on the record. Five come from the response, and one is the time of the check.
valid says whether the number fits a numbering range. It does not say whether the number is in use. score.phone.ehlr answers that.
mcc and mnc identify the serving network by its mobile country and network codes. Add two text fields to store them.
A failed call returns an error object in place of result. The object carries code, message and optional data. An account with no funds left returns code -32004 and the message Low balance. The filter in step 04 stops the run. Zap history lists the run as filtered, and HubSpot is left unchanged.
A timed-out request shows as an error in Zap history. Replay the run from Zap history once the request can go through.
Up to 20 requests per second. 2 seconds average response. Up to 10,000 numbers per request. A flow that runs once per new record sends one request per record.
For records already in your CRM, export a CSV and upload the file in your workspace. Uploads take up to 5 MB and 200,000 rows.
auth.login takes your email and password. The token arrives in the Token response header, and it lasts 24 hours.
Webhooks by Zapier does not pass response headers to later steps. The token arrives in a header. A Code by Zapier step replaces step 03. The code logs in, then runs the check.
Delete step 03 and add Code by Zapier in its place, with the Run JavaScript event.
Code by Zapier runs for up to 30 seconds on Professional and Team plans. The Free plan allows 1 second, too short for two requests.
The code step returns flat fields named phone, valid, line_type, carrier, ported and e164_format. In step 04, filter on Phone. In step 05, map each property to the field of the same name.
The password sits in the Zap. Anyone who can edit it can read the password. Ask your account manager for an API key when you can.
Create your workspace, or walk through your stack with our team.
Make guiden8n guideCRM integrationsAPI reference at doc.scoremachine.ai