How to connect HubSpot and Make (and what to keep manual)

The short answer

1. 01Write the process down: the trigger, the fields, the owner and what should happen when something fails.
2. 02Have a HubSpot super admin approve the Make app, then create the HubSpot connection in Make.
3. 03Choose how the scenario starts: on a schedule or instantly from a webhook.
4. 04Search for the record before creating one, then create or update it.
5. 05Map fields carefully and decide what happens when a value is blank.
6. 06Add error handling and an alert to the owner.
7. 07Test with sample records, then switch it on and watch the first runs.
8. 08Write a one-page runbook and keep the connection on a company-owned account.

When to use Make instead of HubSpot workflows

Use HubSpot workflows for work that stays inside HubSpot: setting properties, rotating owners, enrolling contacts in emails and creating tasks. Use Make when data has to move between HubSpot and another tool, such as a document template, Slack, a spreadsheet, a project tracker or a billing system, or when the logic goes beyond what the workflow editor can do. Many teams use both: a HubSpot workflow handles the steps inside HubSpot and hands off to Make for the rest.

HubSpot workflows are available on Professional and Enterprise subscriptions, not on Free or Starter. Make's HubSpot app works through HubSpot's API, so it can connect to portals on any tier, within the API access that tier includes. For the broader difference between the two kinds of automation, see marketing automation vs workflow automation.

What you need before you start

• A HubSpot super admin, or someone who can reach one, to approve the Make app before the first connection.
• A Make account owned by the company, not by one employee or an outside contractor.
• A written field list: which HubSpot properties the scenario reads and writes, with their internal names and types.
• A few test records you can create, update and delete safely.
• A named owner who receives error alerts and approves changes.

Choosing the trigger: scheduled or instant

HubSpot retries a failed workflow webhook for up to three days, so the same change can arrive more than once. Build the scenario so it's safe to run twice on the same record: search first, then update.

Search before you create

Duplicates are the most common problem in HubSpot + Make builds. Before a scenario creates a contact, company or deal, it should search for an existing record by a stable key, such as email address for contacts or domain for companies, and update that record instead.

Make's HubSpot app includes search modules for contacts, companies, deals and other CRM objects, plus a "Make an API Call" module for anything the standard modules don't cover. If the portal already has duplicates, clean them up first with the CRM audit checklist.

Mapping fields without breaking reports

• Use internal names and matching types: dropdown and checkbox values must match HubSpot's options exactly.
• Decide what a blank value does: skip the field or clear it in HubSpot. Clearing a field by accident is an easy way to lose data.
• Protect the properties reports depend on: don't let a scenario overwrite lifecycle stage, original source or owner unless that is the point of the build.
• Record where changes come from: a property such as "last updated by automation" shows anyone where a change came from.

Errors, alerts and ownership

• Add error handling to modules that write to HubSpot, so one bad record doesn't stop the run for everything else.
• Send failures to the owner in Slack or email, with a link to the record.
• Watch the first week of runs in Make's history before you stop checking.
• Write a one-page runbook: what the scenario does, where it runs, which accounts it uses and how to pause it.
• Keep the connection on a company-controlled account. In this Make and Slack project closeout build, the Make environment and credentials were transferred to a company-controlled account for long-term continuity.

What to keep manual

Connecting HubSpot and Make makes it easy to automate everything. These steps should still end with a person:

• Messages to clients: Make can draft and queue them; a person sends them.
• Merging and deleting records: Make can flag likely duplicates; a person approves the merge.
• Lifecycle and disqualification decisions: a scenario can apply agreed rules; a person handles the exceptions.
• Anything AI wrote: review it before it reaches a record that a client or salesperson will read.

Common HubSpot + Make builds

For a real CRM-to-document example built in Make, see the contract generation case study.