CRM integration for lead handoff

A lead scoring system with no CRM integration produces qualified leads that exist only in the application database — invisible to the sales team until someone manually exports and imports them. iso-25010:2011 reliability.fault-tolerance applies because the lead handoff is a single-point-of-human-failure: if no one runs the export, the lead is never worked. Beyond operational risk, missing bidirectional sync means the CRM's deal stage and rep assignment cannot inform sequence behavior — a contact who has already progressed to negotiation continues receiving top-of-funnel nurture emails because the sequencing system has no visibility into CRM state.

Trigger CRM contact creation and task assignment in fireThresholdAction when a lead crosses the sales-notification threshold. Sync at minimum three fields: email, lead score, and lifecycle stage.

import { Client as HubSpotClient } from '@hubspot/api-client'
const hubspot = new HubSpotClient({ accessToken: process.env.HUBSPOT_ACCESS_TOKEN })

async function handoffToSales(contact: Contact, score: number) {
  await hubspot.crm.contacts.basicApi.create({
    properties: {
      email: contact.email,
      firstname: contact.firstName,
      lastname: contact.lastName,
      lead_score: String(score),
      hs_lead_status: 'IN_PROGRESS',
    }
  })

  await hubspot.crm.objects.tasks.basicApi.create({
    properties: {
      hs_task_subject: `Hot Lead: ${contact.email} (score: ${score})`,
      hs_task_status: 'NOT_STARTED',
      hs_task_priority: 'HIGH',
      hs_timestamp: String(Date.now()),
    }
  })
}

Store the CRM contact ID on your local contact record after creation to enable future bidirectional sync (e.g., pulling deal stage back to suppress sequences for closed-won or closed-lost contacts).