How to Connect HubSpot CRM with Make (2026)

How to Connect HubSpot CRM with Make

HubSpot CRM and Make (formerly Integromat) together deliver enterprise-level automation at a fraction of the cost of custom development. Make's visual scenario builder allows you to create complex, multi-step workflows that move data in and out of HubSpot with conditional logic, data transformations, and error handling built in.

While HubSpot's native Workflows feature handles internal automation well, Make extends HubSpot's reach to hundreds of external applications. Make's HubSpot module supports full CRUD operations on contacts, companies, deals, tickets, and custom objects, plus triggers for record creation and updates, form submissions, and engagement events.

Make is a strong choice over Zapier for teams that need more complex branching logic, data aggregation, or higher-volume automation at a lower per-operation cost.

Integration Methods

Native Integration Setup

Step 1: Create a Make Scenario

Log in to Make and click Create a new scenario. Click the + button to add a module and search for "HubSpot CRM."

Step 2: Connect Your HubSpot Account

Click Add next to the connection field. Make will redirect you to HubSpot's OAuth page. Sign in and select the portal you want to connect. Authorize the requested scopes.

Step 3: Choose a Trigger Module

Select a trigger such as Watch Contacts, Watch Deals, Watch Form Submissions, or Watch Events. Configure the polling interval and any filters.

Step 4: Add Action Modules

Add downstream modules for your target applications. Between modules, use Make's built-in tools like Router (for branching), Aggregator (for batching), and Iterator (for processing arrays).

Step 5: Map Data and Add Error Handling

Map HubSpot fields to action module fields using Make's visual mapper. Add error handlers to manage API failures gracefully. Set up the scenario schedule and activate it.

What Data Syncs

Use Cases

Multi-System Data Enrichment Pipeline

When a new HubSpot contact is created, Make triggers a scenario that enriches the record with data from Clearbit, checks for duplicates against your data warehouse, and updates the HubSpot contact with enriched company info, revenue data, and industry classification.

Complex Deal Stage Workflows

When a HubSpot deal moves to a specific stage, Make uses a Router module to execute different paths: generating a contract in PandaDoc, notifying the finance team via Slack, creating a project in Asana, and updating a forecast spreadsheet in Google Sheets.

Automation Recipes

• When: a HubSpot form is submitted → Then: enrich the contact, score the lead, and route to the correct sales rep via Slack
• When: a HubSpot deal closes → Then: generate an invoice, create an onboarding project, and send a welcome email sequence
• When: a HubSpot contact property changes → Then: sync the update to five other connected platforms in parallel
• When: a CSV file is uploaded to Google Drive → Then: parse and import each row as a HubSpot contact with deduplication

Troubleshooting

Scenario stops running unexpectedly

Check the scenario execution log in Make for specific error messages. Common causes include expired HubSpot OAuth tokens (re-authenticate), HubSpot API rate limits (add a delay between operations), or data type mismatches in field mapping.

Missing custom properties in HubSpot module

Make caches the HubSpot schema. Click the Refresh button on the HubSpot module to reload available properties. Newly created custom properties may take a moment to appear.

Limitations

Make uses polling to detect HubSpot changes, so there is a built-in delay based on your scenario schedule. Real-time processing requires configuring HubSpot Workflow webhook actions to trigger Make scenarios via instant webhooks. Make's free plan is limited to 1,000 operations per month. Complex scenarios with many modules consume operations quickly. HubSpot API rate limits (100 requests per 10 seconds for OAuth apps) apply to all Make operations.