ScoreMachine
Login

Integrations · CRM

Connect Phone and Email Validation to Your CRM

Run ScoreMachine checks when a record is created, and write the results to the record. Build it on an automation platform, on the CRM itself, or with our solutions team.

Your first $5 of validations are on us, valid for 30 days. No card required.

Three Ways to Connect a CRM

01

Use an automation platform

Zapier, Make and n8n call the API from their own HTTP step. Each guide builds one flow, trigger to fields.

02

Build on the CRM's developer platform

Most CRMs run your code or an HTTP call when a record is created. The cards below name the tools for each.

03

Ask our solutions team

Our solutions team builds custom CRM integrations on request, on your CRM's own developer platform.

CRM by CRM

Each CRM below supports custom integration development. Each card names the developer platform, the event that starts a check, and where results land.

HubSpot

Build withHubSpot's developer platform, with project-based apps built and deployed through the HubSpot CLI.
Starts onA webhook subscription to contact object.creation, or a custom code action in a workflow.
Results land inCustom contact properties. App cards show them on the contact record.
AccessPrivate apps use a static token or OAuth. Marketplace apps use OAuth.

Custom code actions need Data Hub Professional or Enterprise, and finish within 20 seconds.

Pipedrive

Build withApps registered in Pipedrive's Developer Hub, private or listed on the Pipedrive Marketplace.
Starts onA webhooks v2 subscription with event_object person and event_action create.
Results land inCustom person fields. JSON panels or custom UI extensions show them in the detail view.
AccessApps use OAuth 2.0. Scripts use a personal API token.

Kommo

Build withPrivate integrations for one account, or public integrations on the Kommo Marketplace after a code audit.
Starts onA webhook on contact or lead events. A Digital Pipeline widget can also fire when a lead enters a stage.
Results land inCustom fields on contacts and leads, written through the CRM API. Widgets built with the Web SDK show them in Kommo.
AccessOAuth 2.0, or a long-lived token for private integrations, valid for 1 day to 5 years.

Salesforce

Build withExternal Client Apps. From Spring '26, Salesforce no longer lets customers create new connected apps.
Starts onA record-triggered flow with the HTTP Callout action, which needs no code. An Apex callout is the coded route.
Results land inCustom fields on Contact or Lead, with API names ending in __c.
AccessA Named Credential and an External Credential hold the ScoreMachine key. Apps are listed on AppExchange.

Zoho CRM

Build withDeluge functions in Zoho CRM, or extensions from the Zoho Developer Console, listed on Zoho Marketplace.
Starts onA workflow rule that runs a function or a webhook when a record is created.
Results land inCustom fields on the Contacts or Leads module.
AccessDeluge's invokeurl task sends the Token header with each request. The task times out after 40 seconds.

Microsoft Dynamics 365 Sales

Build withDataverse plug-ins in C#, or Power Automate flows with a custom connector.
Starts onA plug-in on the contact's Create message, or a flow triggered by a new row.
Results land inCustom columns on the contact table.
AccessPlug-ins call external services over HTTPS with HttpClient, by DNS name only.

Bitrix24

Build withThe Bitrix24 REST API, as a local application or an app on Bitrix24 Market.
Starts onAn outbound webhook that posts to your handler when an event fires, such as a new contact.
Results land inCustom fields on contacts and leads, written back through the REST API.
AccessInbound webhooks call REST methods through a secret URL, with their creator's permissions.

Freshsales

Build withThe Freshworks Developer Platform and its FDK, with apps listed on Freshworks Marketplace.
Starts onA serverless app that reacts to product events, such as a contact being created.
Results land inCustom fields on the contact.
AccessThe Freshsales API authenticates with an API key.

monday CRM

Build withThe monday apps framework, with apps listed on the monday App Marketplace.
Starts onA workflow block, a custom trigger or action that calls your app's public endpoint.
Results land inColumns on the contact's item, written through the monday GraphQL API.
AccessApps use OAuth. Scripts use a personal API token.

Close

Build withThe Close API, with OAuth apps listed in the Close integrations directory.
Starts onA webhook subscription on lead or contact events.
Results land inCustom fields on the lead or contact.
AccessAPI keys for scripts and backend jobs. OAuth 2.0 for integrations other users install.

Custom Integrations by Our Solutions Team

Our solutions team builds custom CRM integrations on request. The integration runs on your CRM's own developer platform. It covers the trigger, the check and the result fields.

What the team builds

  • A check on every new record, with the phone and email methods you choose.
  • A single pass over the records already in your CRM.
  • Custom fields for the results, named to your conventions.
  • A panel or card that shows the results on the record, where the CRM supports one.

What to send us

  • The CRM, and its edition or plan.
  • The objects to check, such as contacts and leads.
  • The fields that hold phone numbers and email addresses.
  • How many records a month the CRM creates.

Frequently asked questions

Run the Checks Inside Your CRM

Create your workspace, or walk through your CRM with our team.

Zapier guideMake guiden8n guidePhone ValidationEmail Validation