Create a HubSpot CRM contact from each new MoClients lead

When MoClients creates a new lead, this workflow adds that person to HubSpot CRM as a contact, so your sales team can work every lead from HubSpot without copying details across.

MoClients

HubSpot CRM

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.6k sites Free to import

The Create a HubSpot CRM contact from each new MoClients lead workflow on the FlowMattic canvas, with 2 steps across MoClients, HubSpot CRM — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Leads that stay in MoClients are easy to lose track of when the rest of your sales process runs in HubSpot. Copying each one by hand takes time and invites typos. This workflow puts every new MoClients lead into HubSpot CRM as a contact.

The MoClients trigger, New Lead, fires when a lead is created in your MoClients account. Its details become values you can map, and a test run shows which ones MoClients sends.

The HubSpot CRM step, Create Contact, then creates a contact from the values you map, usually the email address and name at least. It is a create-only action. If the lead's email already belongs to a HubSpot contact, HubSpot may refuse the request, and Task History shows its response for that run.

Agency handing leads to a HubSpot sales team

Leads collected in MoClients appear in HubSpot as contacts, where reps already log calls and build deals.

Starting HubSpot sequences or workflows

Once the contact exists in HubSpot, your own HubSpot automations, such as lists or sequences, can pick it up from there.

One contact record for reporting

Sales managers who report from HubSpot see MoClients leads counted alongside contacts from other sources.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
MoClients New Lead
Starts a run each time MoClients records a fresh lead in your account. Connect your MoClients account on import and create a test lead so FlowMattic captures the fields it sends.
Step 2Action
HubSpot CRM Create Contact
Turns the MoClients lead into a new HubSpot CRM contact. Connect HubSpot, then map the MoClients email, name and any other details you want stored on the new contact.

What you need

FlowMatticCore
MoClients AccountAccount
HubSpot CRM AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a Filter after the trigger that continues only when the lead's email is not empty, so HubSpot is never asked to create a contact without one.
To create a deal for each lead as well, add HubSpot's Create Deal action after the contact step and map the lead's details into it.
Map a fixed value such as MoClients into a HubSpot contact property you use for lead source, so you can tell these contacts apart later.

Questions about this workflow

What happens if the MoClients lead is already a HubSpot contact?

Create Contact only creates new records. HubSpot may refuse a duplicate email, and the run's Task History entry shows HubSpot's response. Nothing is updated on the existing contact.

Which MoClients details reach HubSpot?

Just the values you place in the HubSpot step's fields. Run a test lead after import to see what MoClients sends, then match each value to a HubSpot field.

Are leads already in MoClients copied to HubSpot?

No. The workflow handles leads created after you turn it on. Older leads stay in MoClients unless you move them yourself.

Does editing a MoClients lead later change the HubSpot contact?

No. The trigger fires once, when the lead is created in MoClients. Later edits there don't start a run, so update the HubSpot contact yourself if details change.