Here's something that happens in almost every HubSpot portal we've audited.

A new contact lands in the CRM, imported from a CSV, or synced in via an API integration. The contact exists. The data is there. And then...nothing happens. No lead record. No task. No rep picks it up. It just sits in the contacts database until someone eventually notices or a follow-up sequence eventually catches it.

The fix is a single workflow. Once it's on, every new contact that gets enrolled automatically triggers a lead record in HubSpot's prospecting workspace, ready for a rep to work the moment it lands.

Why This Gap Exists

HubSpot's leads object and the contact record are two separate things. A contact being in your CRM doesn't automatically mean they show up as a lead in the Sales Workspace for your reps to act on.

That distinction matters more than it sounds. The prospecting workspace is where your sales team lives day-to-day, their queue, their tasks, their pipeline view. If a new contact never becomes a lead record, it's effectively invisible to any rep working from that space.

For contacts that come in via form fills, this isn't usually a problem, there's often an existing workflow or manual process. But for contacts arriving through API integrations, data enrichment tools, or bulk imports, there's typically no automatic handoff. The contact lands. The lead never gets created. Your team follows up late, or not at all.

What You'll Need

  • Sales Hub Professional or Enterprise - The leads object and the "Create record" workflow action are available at these tiers.
  • Admin or workflow permissions in HubSpot.

How to Set it Up

Step 1: Create a Contact-Based Workflow

Go to Automation > Workflows and create a new Contact-based workflow.

Set the enrolment trigger to "Contact is enrolled" - specifically, when a contact is created or when a contact meets a filter condition that identifies them as a new inbound lead. A clean option here is:

  • Trigger: Contact property - Create date - is known

This fires as soon as a contact record exists. If you want to scope it to specific sources (e.g., only contacts imported via API or from a specific list), add a filter condition at this point:

  • Trigger: Contact property - Original source - is equal to - API (or Import, depending on your use case)

Make sure re-enrolment is turned off. You don't want a lead created every time the contact record is updated, just once, on first creation.

Step 2: Add the "Create Record" Action

Inside the workflow, click the + button to add an action. Search for and select Create record.

In the dropdown that appears, select Lead as the record type.

From here, you can populate the following fields on the lead record:

  • Lead label - give it a name, e.g., the contact's name or a source identifier like "API Import - [Date]". You can use personalisation tokens here.
  • Lead pipeline stage - set this to New to drop it straight into the front of your reps' prospecting queue
  • Lead type - Inbound or Outbound depending on the source
  • Owner - set to Contact's existing owner so it routes to the right rep automatically. If the contact has no owner yet, the lead will be unassigned, worth setting up a default owner or round-robin logic as a follow-on step.

Per HubSpot's documentation, there are no required fields when creating a lead via the "Create record" action. But populating Label and Pipeline Stage is recommended, without them, the lead lands in your workspace with no context and no stage, which creates more friction for the rep picking it up.

Step 3: Save and Turn On

Save the workflow and turn it on.

From this point, every contact that meets your enrolment trigger will automatically get a corresponding lead record created in the Sales Workspace under Sales > Sales Workspace > Leads. Reps will see it in their queue with stage set to New, ready to work.

A Few Things Worth Knowing

Leads are associated, not duplicated. The lead record is linked to the contact, it doesn't replace it or create a second contact. Think of it like a deal: the deal is associated with a contact, but they're separate objects with separate purposes. You can have multiple lead records for the same contact to track different qualification attempts or pipeline entries over time.

This doesn't replace lifecycle stages. Lead records and lifecycle stages coexist. A contact can be a Marketing Qualified Lead (MQL) by lifecycle stage while simultaneously having an open lead record in the prospecting workspace. They serve different purposes - lifecycle stages describe where someone is in the funnel; the lead record is the active sales task.

HubSpot also has native lead automation. Under Settings > Objects > Leads > Pipelines > Automate, you can toggle on automatic lead creation based on lifecycle stage changes. This is a simpler setup for some use cases, if you only want leads created when a contact reaches SQL status, the native automation is cleaner. The workflow approach covered above gives you more control over the trigger conditions, which is why it's useful for import or API-based contact creation specifically.

Watch for duplicates if you run both. If you have native lifecycle-stage-based lead automation enabled AND this workflow, you may end up with duplicate lead records for the same contact. Check your existing settings before turning this on.

The Bigger Picture

The whole point of HubSpot's leads object and the prospecting workspace is to give sales teams a clean, structured queue, separate from the noise of the full contacts database. But that only works if leads actually get into the workspace in the first place.

For contacts coming from forms and meetings, the handoff usually happens. For everything else, imports, integrations, enrichment tools, it often doesn't. This workflow closes that gap. It's a five-minute build that means no new contact ever sits invisible in your CRM while your reps have no idea it exists.

Want Us to Look at Your Lead Routing Setup?

If this surfaces a bigger question, how your leads are being assigned, whether your prospecting workspace is actually set up to reflect your sales process, or why your team isn't working the leads that are there, that's exactly the kind of thing we dig into.

Neighbourhood is a Diamond HubSpot Partner. We've been inside enough portals to know that lead routing gaps are one of the most common places revenue quietly leaks. Give us a shout and we'll take a look.

Talk to us about your HubSpot setup.

Catch the Rest of the Series

We constantly break down HubSpot hacks like this one. Short, practical, and actually useful. Follow us on Facebook and YouTube if you'd rather watch someone click through it than read about it.

Happy HubSpotting!