How to Automate CRM Updates with Make

Build a Make scenario that keeps HubSpot contacts current: the Create or Update a Contact module matches by email, so records update instead of duplicating.

By Galactic News Editorial · Published 2026-11-07T19:31:54+00:00 · Updated 2026-11-07T19:31:54+00:00

How to Automate CRM Updates with Make

Make automates work through scenarios. A scenario is a chain of modules. Each module performs one action in an app, such as creating or updating a record. For CRM updates, Make's HubSpot CRM app includes a Create or Update a Contact module. It matches records by email address. Existing contacts get updated, and new ones get created. This guide builds that scenario step by step, using Make's own documentation and app pages.

What you need before you start

• A Make account. New users are assigned a free account when they register.
• Access to the CRM you want to update, such as a HubSpot account.
• A source of updates, such as a form, a spreadsheet, or another app.
• One field that identifies each record. For contacts, that field is the email address.

How to automate CRM updates with Make, step by step

1. Create a new scenario. In Make, click Create scenario. The scenario builder opens with an empty canvas.
2. Add the trigger module. Choose the app where updates begin. Pick its Watch module, such as watching new form responses or new spreadsheet rows.
3. Connect the source app. Create a connection and authorize Make to read the source data.
4. Add the HubSpot CRM module. Click the plus icon beside the trigger. Search for HubSpot CRM. Select Create or Update a Contact.
5. Create the HubSpot connection. Authorize Make to access your HubSpot account.
6. Map the fields. Map the email address first. Make's module creates a new contact if that email does not exist. Otherwise, it updates the existing contact. Then map name, phone, company, and any other properties you maintain.
7. Test with Run once. Click Run once, then submit a test record in the source app. Watch each module run in sequence.
8. Check the CRM record. Open the contact in HubSpot. Confirm every mapped field arrived correctly.
9. Test the update path. Run once again with the same email and one changed field. The contact should update in place, not duplicate.
10. Set the schedule. Click the clock icon on the trigger module to open Schedule settings. Choose how often the scenario runs.
11. Save and activate. Save the scenario, give it a clear name, and click Activate scenario. Make now applies your CRM updates on schedule.

Useful module patterns for CRM upkeep

Start from a template when one fits

You do not have to build every scenario from a blank canvas. Make publishes ready-made templates for its app pairings. Its integration pages invite you to explore templates and start automating in minutes. The Zoom and HubSpot pairing, for example, offers a template that creates or updates a HubSpot contact for every new meeting registrant. Open the template inside your Make account. Then adjust the field mapping to match your own CRM properties. Templates also reveal which modules Make expects you to combine. That makes them useful even when you build your own version afterwards.

Keep the scenario accurate over time

A scenario keeps the settings you last saved. When your source form or CRM properties change, update the mapping to match. After editing any module, click Save. Then click Run once and send a fresh test record through. Confirm the change inside HubSpot before the next scheduled run. Also remember how Watch triggers behave. A Watch module collects new items when the scenario runs. Your schedule therefore sets how fresh the CRM data can be. A scenario that runs every few hours cannot deliver minute-by-minute updates. Set the interval to match the freshness your team actually needs.

Why the email match matters

Most CRM duplicates start with blind record creation. A plain Create a Contact module always adds a new record. The Create or Update a Contact module behaves differently. It checks the email in the properties first. If no contact has that email, it creates one. If a contact already has it, that contact receives the update. This single choice keeps routine syncs from filling the CRM with copies. Keep email mapped in every scenario that writes contacts.

Limits to know before you start

• The upsert logic keys on email. Records without an email need a search-based pattern instead.
• Update a Contact works by record ID. You must fetch or store the ID first.
• Scheduled scenarios only run while they are active. Activating the scenario is a separate step from saving it.
• Some HubSpot modules are marked legacy or deprecated on Make's app pages. Check the module list when you build, and pick the current version.